-
Notifications
You must be signed in to change notification settings - Fork 696
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
Zombienet upgrade test #5794
base: master
Are you sure you want to change the base?
Zombienet upgrade test #5794
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.
Nice thank you, we can we use this as a scaffolding for adding the checks I suggested here: #5817, can be done as a follow-up.
spec_name: create_runtime_str!("rococo"), | ||
impl_name: create_runtime_str!("parity-rococo-v2.0"), | ||
authoring_version: 0, | ||
spec_version: 1_016_000, |
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.
I would extract out:
CONST SPEC_VERSION: 1_015_000 and then here I would use SPEC_VERSION + 1.
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.
Sounds good 👍
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.
can extract out, I will leave this way.
error: only numeric literals (e.g. `10`) are supported here
--> polkadot-sdk/polkadot/runtime/rococo/src/lib.rs:187:16
|
187 | spec_version: SPEC_VERSION,
Thx!
.with_node(|node| { | ||
node.with_name("latest-release") | ||
// used for getting the chain-spec | ||
.with_image("parity/polkadot:latest") |
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.
Can we somehow use the exact runtime-image that roco chain is currently using, or at least the last stable release version, since the upgrades happened all at once.
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.
Add zombienet test for upgrading runtime
pr
We use a version built in the pipeline (of rococo-runtime) with the
spec_version
incremented to perform the upgrade and verify then the block production and the expected version.Thx!
NOTE: This tests is behind the
zombienet
feature and you can run with