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
@mordamax and I figure it makes sense to make the bench bot also run the release weight benchmarks, which are currently still ran manually by RelEng on bm4, 5, & 6 (not BM3).
The way it works now is that it runs benches for all pallets in per-runtime batches, so we have 4 jobs right now (rococo, westend, kusama, polkadot), and then we're manually applying the changes to our release branch. Having only 3 machines to run in parallel, we can't run them all at once - so i think it would make sense to
add a 4th bm machine for this
allow us to queue these jobs using the bench bot
commit the results back to the pr/branch where it was triggered
This is essentially very similar to what it does right now when ran for individual pallets in a PR.
The text was updated successfully, but these errors were encountered:
@mordamax and I figure it makes sense to make the bench bot also run the release weight benchmarks, which are currently still ran manually by RelEng on bm4, 5, & 6 (not BM3).
The way it works now is that it runs benches for all pallets in per-runtime batches, so we have 4 jobs right now (rococo, westend, kusama, polkadot), and then we're manually applying the changes to our release branch. Having only 3 machines to run in parallel, we can't run them all at once - so i think it would make sense to
This is essentially very similar to what it does right now when ran for individual pallets in a PR.
The text was updated successfully, but these errors were encountered: