fix: get try-runtime to work again #800
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It took my some time to realize that when you use
try-runtime, all pallets must now enable"frame-support/try-runtime". This didn't use to be the case. While trying to link the PR that changed this, I found they actually warn people about it there. Would have saved me a lot of time if I'd seen that earlier..Anyway, it works now, including console output (that didn't work in the past). Usage is e.g.
RUST_LOG=info cargo run --bin interbtc-parachain --features rococo-native --release --features try-runtime -- try-runtime --execution=native --chain=interlay-latest --no-spec-check-panic on-runtime-upgrade live --uri 'wss://api.interlay.io:443/parachain'