You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
paritytech/polkadot#4342 introduces new polkadot-cli command which basically checks if the machine can compile kusama runtime fast enough. For this we need some kind of time limits obtained from the reference machine.
This PR also includes a crate for generating these limits in a file. Is it feasible to extend the bot to do something like:
# checkout the given branchcd node/test/performance-test
cargo run --release --bin gen-ref-constants
# once it finishes, node/test/performance-test/src/constants.rs is generated
cargo +nightly fmt
# commit new file and push it
I'm not sure since there's
This is a substrate-only bot at the moment.
in the README.
The text was updated successfully, but these errors were encountered:
@slumber 1) since kusama/polkadot runtimes are not part of polkadot-sdk, will that be needed for westend & rococo?
2) how often would people need to run this within PR ?
@slumber 1) since kusama/polkadot runtimes are not part of polkadot-sdk, will that be needed for westend & rococo? 2) how often would people need to run this within PR ?
This command was removed from polkadot cli, hence the issue is no longer relevant
paritytech/polkadot#4342 introduces new polkadot-cli command which basically checks if the machine can compile kusama runtime fast enough. For this we need some kind of time limits obtained from the reference machine.
This PR also includes a crate for generating these limits in a file. Is it feasible to extend the bot to do something like:
I'm not sure since there's
in the README.
The text was updated successfully, but these errors were encountered: