Repository navigation
Debug files for https://github.com/paritytech/try-runtime-cli/issues/53
Pre-releaseFiles related to paritytech#53
git branch
* (HEAD detached at v0.3.4)
simson@tama:~/nodle/work/try-runtime-cli$ cargo run -- --runtime ticket-53/runtime_eden.wasm on-runtime-upgrade --checks=none snap -p ticket-53/snap
Finished dev [unoptimized + debuginfo] target(s) in 0.36s
Running target/debug/try-runtime --runtime ticket-53/runtime_eden.wasm on-runtime-upgrade --checks=none snap -p ticket-53/snap
[2023-11-07T03:56:43Z INFO remote-ext] Loading snapshot from "ticket-53/snap"
✅ Loaded snapshot (2.08s)
[2023-11-07T03:56:46Z INFO remote-ext] initialized state externalities with storage root 0x96461e4db4dbe53604e2f67063595d0f201a59e3635828680666f9aec6d6d259 and state_version V0
[2023-11-07T03:56:46Z INFO try-runtime::cli] Original runtime [Name: RuntimeString::Owned("nodle-para")] [Version: 23] [Code hash: 0xae58...e0f9]
[2023-11-07T03:56:47Z INFO try-runtime::cli] New runtime [Name: RuntimeString::Owned("nodle-para")] [Version: 25] [Code hash: 0xdd47...f334]
[2023-11-07T03:56:47Z INFO try_runtime_core::commands::on_runtime_upgrade] 🔬 Running TryRuntime_on_runtime_upgrade with checks: None
[2023-11-07T03:56:58Z INFO runtime::frame-support] StorageVersion(1) vs current storage version StorageVersion(1)
[2023-11-07T03:56:58Z ERROR try-runtime::cli] failed to generate compact proof: TrieError(InvalidStateRoot(0x868e46de038c23f89652a0763c83831c852728f5d1e42ea98181364ff6c6ce22))
[2023-11-07T03:56:58Z INFO try-runtime::cli] PoV size (zstd-compressed compact proof): 10 B. For parachains, it's your responsibility to verify that a PoV of this size fits within any relaychain constraints.
[2023-11-07T03:56:58Z INFO try-runtime::cli] Consumed ref_time: 0s (0.00% of max 0.5s)
[2023-11-07T03:56:58Z INFO try-runtime::cli] ✅ TryRuntime_on_runtime_upgrade executed without errors or weight safety warnings. Please note this does not guarantee a successful runtime upgrade. Always test your runtime upgrade with recent state, and ensure that the weight usage of your migrations will not drastically differ between testing and actual on-chain execution.