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

Add region set options to more tests. #1496

Merged
merged 3 commits into from
Oct 11, 2024
Merged

Add region set options to more tests. #1496

merged 3 commits into from
Oct 11, 2024

Conversation

leftwo
Copy link
Contributor

@leftwo leftwo commented Oct 7, 2024

Give test_live_repair, test_replace_special, and test_replay an option to indicate how many region sets should be created for the test. This allows us to use the same script to test single and multiple sub-volumes.

Updated a few of the tests to no longer run a smaller test in a loop, but instead just run a longer test. This makes better sense when testing many sub-volumes as a smaller test might not cover everything. It has the side effect of not printing regular status messages, but if we find that is important we can come up with another way of displaying test progress.

Future PRs will use these options to increase test coverage on multiple sub-volumes.

Give test_live_repair, test_replace_special, and test_replay an option
to indicate how many region sets should be created for the test.  This
allows us to use the same script to test single and multiple
sub-volumes.

Updated a few of the tests to no longer run a smaller test in a loop,
but instead just run a longer test.  This makes better sense when
testing many sub-volumes as a smaller test might not cover everything.
It has the side effect of not printing regular status messages, but if
we find that is important we can come up with another way of displaying
test progress.
if ! "$crucible_test" fill --dsc 127.0.0.1:9998 -q -g "$gen"\
--verify-out "$verify_log" >> "$test_log" 2>&1 ; then
echo Failed on initial verify seed, check "$test_log"
--skip-verify >> "$test_log" 2>&1 ; then
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this just to go faster?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The addition of --skip-verify, yeah, that's just to go a little faster.
We don't bother with the --verify-out any longer because we are not stopping and starting crutest several times, so we no longer need to read in the verify info from the previous loop.

The stopping/starting part of the test here was causing problems when we have multiple region sets. The region set that we ended the previous test loop on might not match up with the region set that we start with by default.

@leftwo leftwo merged commit 93e1df3 into main Oct 11, 2024
19 checks passed
@leftwo leftwo deleted the alan/test-more-regions branch October 11, 2024 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants