Add random-netsplits tc, trace improvements #42
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
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.
WIP. Added a random_netsplits test case to the
locks_leader_SUITE. It currently fails. I've been working on improving thelocks_ttbtracing support, and it now works much better for long-running test cases (dropping the initial trace data and keeping the last 1000 events). A pretty-printed trace with an emacs mode header is generated for each failing test case.The random_netsplits test case is greatly inspired by the locks-test project by @ten0s but I decided to write my own to achieve better integration into the existing test suite.