Experiment: verify secondaries in crash test by recreating expected state as of sequence number #13266
+414
−148
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
archang19
force-pushed
the
stress-test-follower
branch
3 times, most recently
from
e9fdd31 to
bd06353
Compare
archang19
force-pushed
the
stress-test-follower
branch
from
bd06353 to
3316533
Compare
archang19
force-pushed
the
stress-test-follower
branch
from
3316533 to
de7f11c
Compare
archang19
changed the title
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.
Here I experiment with one approach to verify secondaries in the crash tests. I take the most recent
statefile, replay thetracefile up to a certain sequence number, and create anExpectedStaterepresenting the target state as of a particular point in time. ThisExpectedStategets used to run comparisons against the secondary.