Unit test for deadlock detection when testQBFTBlock is set to 1 #1272
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
ricardolyn
reviewed
Oct 28, 2021
jbhurat
force-pushed
the
qbft_transition_deadlock
branch
from
c13c866
to
df27d3a
Compare
jbhurat
force-pushed
the
qbft_transition_deadlock
branch
from
df27d3a
to
acf429e
Compare
ricardolyn
approved these changes
Oct 28, 2021
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.
Commit 2a83106 added a fix for a deadlock that occurred when testQBFTBlock fork block was set to 1. This PR adds a unit test for that fix.