-
Notifications
You must be signed in to change notification settings - Fork 696
Fix/5205 #5206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…er PeerNetwork::run()
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM, but is it feasible to add a test for this behavior?
Arguably, the entire unit / integration test battery is the test. If this code failed to run the requisite state machines correctly, we'd see widespread failures. |
|
|
…is mined Signed-off-by: Jacinta Ferrant <[email protected]>
…mined in the same stacks block Signed-off-by: Jacinta Ferrant <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome. Thanks for fixing that @jferrant!
No worries at all :D Thanks for explaining to me! |
results of the CI failing test (fyi, the cache has been evicted so a full re-run would be required here). tests::nakamoto_integrations::multiple_miners)passes tests::signer::v0::partial_tenure_fork
tests::signer::v0::retry_on_rejectionran for over 10 minutes, same scrolling WARN
tests::signer::v0::empty_sortition
|
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Fixes #5205 so that Nakamoto network state machines run at most once per call to
PeerNetwork::run()