Add iterator refresh to stress test #10766
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@cbi42 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary: added calls to
Iterator::Refresh()inNonBatchedOpsStressTest::TestIterateAgainstExpected(). The testing key range is locked inTestIterateAgainstExpectedso I do not expect this change to provide thorough stress test toIterator::Refresh(). However, it can still be helpful for catching bugs like #10739. Will add calls to refresh inTestIterateonce we support iterator refresh with snapshots.Test plan:
python3 tools/db_crashtest.py whitebox --simple --verify_iterator_with_expected_state_one_in=2