new tools for developers: testing a custom runtime upgrade against released binaries #671
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.
Adds two new jobs to Moonwall, which dont execute in the CI, with the following purpose:
This job is similar to the one we have running in the CI, however this runs with the latest released node binaries, while the CI one runs with the compiled binary.
Developers can test it doing from the
test
folder doing:pnpm moonwall test zombie_simple_template_upgrade_with_latest_releases
if they are upgrading a non-frontier runtime or:pnpm moonwall test zombie_frontier_template_upgrade_with_latest_releases
if they are upgrading a frontier runtimeThis should prevent developers from pushing runtimes that are not compatible with the latest release node (as it happened in the past)
CC @augustocollado