-
Notifications
You must be signed in to change notification settings - Fork 680
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
Add test to demonstrate the failure scenario #1999
Conversation
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.
Is it possible to modify the test so that it's testing not the failure scenario but the expected behavior? E.g., if we remove [should_panic]
and the test passes, that means that we fixed the bug?
yes, if the issue is resolved, two changes would be needed:
|
@dmitry-markin Addressed comments, please merge if looks good, thanks |
Looks good to me, but still need one more approving review to be able to merge. |
The CI pipeline was cancelled due to failure one of the required jobs. |
bot help |
Here's a link to docs |
The change adds a test to show the failure scenario that caused paritytech#1812 to be rolled back (more context: paritytech#493 (comment)) Summary of the scenario: 1. Node has finished downloading up to block 1000 from the peers, from the canonical chain. 2. Peers are undergoing re-org around this time. One of the peers has switched to a non-canonical chain, announces block 1001 from that chain 3. Node downloads 1001 from the peer, and tries to import which would fail (as we don't have the parent block 1000 from the other chain) --------- Co-authored-by: Dmitry Markin <[email protected]>
The change adds a test to show the failure scenario that caused #1812 to be rolled back (more context: #493 (comment))
Summary of the scenario: