test(general): fix endurance test failures #4859
Merged
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.
Prevent running "auto-maintenance" on snapshot create.
Ref:
Context: the test fails because there are concurrent "endurance" runners and each of these advances the clock, some of them significantly (
action{Small,Medium,Large}ClockJump), which causes the clock skewness check to fail when (auto-)maintenance runs. The test maintenance action does not run into this issue because it runs exclusively on its own, that is, other actions have to wait until maintenance completes.