-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Accept only one block in validate_block when upgrading a runtime
#10280
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
As the validation is running the entire time using the same validation code, we can not accept any other blocks after a runtime upgrade was applied.
|
/cmd prdoc --audience node_dev --bump patch |
…e_dev --bump patch'
|
I am assuming the collators already won't produce a multi block collation in that case? |
| .output() | ||
| .expect("Runs the test"); | ||
|
|
||
| assert!(dbg!(String::from_utf8(output.stderr).unwrap()) |
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.
| assert!(dbg!(String::from_utf8(output.stderr).unwrap()) | |
| assert!(String::from_utf8(output.stderr).unwrap() |
| // assert!(dbg!(String::from_utf8(output.stderr).unwrap()) | ||
| // .contains("only one block per PoV is allowed")); |
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.
| // assert!(dbg!(String::from_utf8(output.stderr).unwrap()) | |
| // .contains("only one block per PoV is allowed")); |
…ly-one-block-per-pov' into bkchr-validation-only-one-block-per-pov
Yes |
|
All GitHub workflows were cancelled due to failure one of the required jobs. |
|
Created backport PR for
Please cherry-pick the changes locally and resolve any conflicts. git fetch origin backport-10280-to-stable2506
git worktree add --checkout .worktree/backport-10280-to-stable2506 backport-10280-to-stable2506
cd .worktree/backport-10280-to-stable2506
git reset --hard HEAD^
git cherry-pick -x 4e1d96383b2ae73de8e66ac9f8c8b8580ac9af80
git push --force-with-lease |
|
Created backport PR for
Please cherry-pick the changes locally and resolve any conflicts. git fetch origin backport-10280-to-stable2509
git worktree add --checkout .worktree/backport-10280-to-stable2509 backport-10280-to-stable2509
cd .worktree/backport-10280-to-stable2509
git reset --hard HEAD^
git cherry-pick -x 4e1d96383b2ae73de8e66ac9f8c8b8580ac9af80
git push --force-with-lease |
Backport #10280 into `stable2509` from bkchr. See the [documentation](https://github.com/paritytech/polkadot-sdk/blob/master/docs/BACKPORT.md) on how to use this bot. <!-- # To be used by other automation, do not modify: original-pr-number: #${pull_number} --> --------- Co-authored-by: Bastian Köcher <[email protected]> Co-authored-by: Egor_P <[email protected]> Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
As the validation is running the entire time using the same validation code, we can not accept any other blocks after a runtime upgrade was applied.