Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

minor cleanups to db_crashtest.py #10654

Closed
wants to merge 1 commit into from

Conversation

ajkr
Copy link
Contributor

@ajkr ajkr commented Sep 8, 2022

Expanded all_params to include all parameters crash test may set. Previously, atomic_flush was not included in all_params and thus was not visible to finalize_and_sanitize(). The consequence was manual crash test runs could provide unsafe combinations of parameters to db_stress. For example, running db_crashtest.py with -atomic_flush=0 could cause db_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 a db_crashtest.py argument. So I renamed enable_tiered_storage to test_tiered_storage for db_crashtest.py, which appears more conventional anyways.

Expanded `all_params` to include all parameters crash test may set.
Previously, `atomic_flush` was not included in `all_params` and thus was
not visible to `finalize_and_sanitize()`. The consequence was manual
crash test runs could provide unsafe combinations of parameters to
`db_stress`. For example, running `db_crashtest.py` with `-atomic_flush=0`
could cause `db_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 for
both `db_stress` and `db_crashtest.py`. So I renamed
`enable_tiered_storage` to `test_tiered_storage` for `db_crashtest.py`,
which appears more conventional anyways.
@facebook-github-bot
Copy link
Contributor

@ajkr has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

1 similar comment
@facebook-github-bot
Copy link
Contributor

@ajkr has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

Copy link
Contributor

@hx235 hx235 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! And my github notification email proves to work now!

@ajkr
Copy link
Contributor Author

ajkr commented Sep 9, 2022

Thanks for the review!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants