Open sameh-farouk opened 3 weeks ago
I found that this issue is also reproducible in the development branch with any migration. I also verified that it has been there since we upgraded to Polkadot v1.0.0. It Seems the try-runtime is broken with that release.
@renauter brought good news that the migration issue is fixed in Polkadot v1.1.0. He also pinpointed the related PR containing this bug fix https://github.com/paritytech/substrate/pull/14793 from the v1.1.0 release notes.
He already has a draft pull request to upgrade to v1.1.0, so we will push it forward.
Indeed, https://github.com/threefoldtech/tfchain/pull/902 should fix this issue
I'm currently testing a storage migration on my branch development-contracts-billing-refactor with try-runtime but encountered an issue where the weight returned by ʼExecutive::try_runtime_upgrade(checks).unwrap();ʼ is 0.
The migration logic itself seems to be working correctly, as logging within the migration function shows that the proper weight is being calculated and returned. However, when running try-runtime-cli, even though the migration logic is triggered, the reported runtime ref_time consumed is 0.
End of logs:
I tried to pass --checks=none and --checks=all to on-runtime-upgrade, but the result remains the same—0 weight is reported, even though the migration logic is executed always as expected.