minor cleanups to db_crashtest.py #10654
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Expanded
all_params
to include all parameters crash test may set. Previously,atomic_flush
was not included inall_params
and thus was not visible tofinalize_and_sanitize()
. The consequence was manual crash test runs could provide unsafe combinations of parameters todb_stress
. For example, runningdb_crashtest.py
with-atomic_flush=0
could causedb_stress
to run with-atomic_flush=0 -disable_wal=1
, which is known to produce inconsistencies across column families.While expanding
all_params
, I found we cannot have an entry in it with the same name as adb_crashtest.py
argument. So I renamedenable_tiered_storage
totest_tiered_storage
fordb_crashtest.py
, which appears more conventional anyways.