adding flushall after memtier benchmark failure. #320
Merged
Conversation
This file contains hidden or 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
…se may be in a corrupted state for the next test
slice4e
changed the title
fcostaoliveira
approved these changes
Oct 15, 2025
slice4e
added a commit
to slice4e/redis-benchmarks-specification
that referenced
this pull request
Oct 16, 2025
Apply black formatting to runner.py for FLUSHALL changes from PR redis#320 to comply with CI code style checks.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Otherwise what may happen is that a test fails (after a timeout) but some data has been inserted into redis. The following test will find the database to contain unexpected data and fail.