-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[ci] Add short benchmarks to the pipeline #5188
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow very cool! Nearly suspicious that they all succeed 😆
@brunopgalvao You can incorporate rococo here as well, once rococo benches work.
Co-authored-by: Mara Robin B. <[email protected]>
I double checked and something is not quite right, but we can probably already merge this and fix that later: The polkadot benchmark --execution wasm --wasm-execution compiled --chain polkadot-dev --pallet "runtime_parachains::ump" --extrinsic "*" --steps 1 --repeat 1 We can probably replace the script with just: polkadot benchmark --execution wasm --wasm-execution compiled --chain ${runtime}-dev --pallet "*" --extrinsic "*" --steps 1 --repeat 1 |
Should be fixed now. |
bot rebase |
Rebasing |
@ggwpez it seems that rebase didn't help. Should I make short-benchmarks |
It helped, but now a different one fails 🤦 ( |
* master: Try to fix out of view statements (#5177) Companion for Substrate#11107 (#5197) paras: `include_pvf_check_statement` rt bench (#4938) [ci] Run short benchmarks only in PR pipelines (#5200) Companion for paritytech/substrate#10242 (#4862) [ci] Add short benchmarks to the pipeline (#5188) upgrade coarsetime to 0.1.22 to fix a potential panic (#5193) Update docs and enable DOT-over-XCM (#4809) enable disputes on all chains (#5182) companion for validator self-vote in bags (#5088) Extract MAX_FINALITY_LAG constant from relay_chain_selection (#5159)
The PR adds short benchmarks and removes
check-runtime-benchmarks
job as suggested in https:/paritytech/ci_cd/issues/353