-
Notifications
You must be signed in to change notification settings - Fork 740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-establish pallet_revive weights baseline #5845
Conversation
mordamax
commented
Sep 26, 2024
•
edited
Loading
edited
- update baseline for pallet_revive
- update cmd pipeline name
- Fix compilation after renaming some of benchmarks in pallet_revive. [Runtime Dev]. Changed the "instr" benchmark so that it should no longer return to little weight. It is still bogus but at least benchmarking should not work. (by @athei )
It doesn't compile because we renamed some benchmarks but never fixed the places where the benchmarks were used. The benchmarking worked fine I guess just need some follow up fixes here. I can push the fixes to this PR later. |
So I fixed the compilation. But because the |
/cmd bench --pallet=pallet_revive --runtime=dev |
I changed the |
Do you know why it didn't work? |
Co-authored-by: Alexander Samusev <[email protected]>
investigating... |
/cmd bench --pallet=pallet_revive --runtime=dev --clean |
Command "bench --pallet=pallet_revive --runtime=dev --clean" has started 🚀 See logs here |
Command "bench --pallet=pallet_revive --runtime=dev --clean" has started 🚀 See logs here |
Command "bench --pallet=pallet_revive --runtime=dev --clean" has failed ❌! See logs here |
bot bench substrate-pallet --pallet=pallet_revive |
@mordamax https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7477550 was started for your command Comment |
…=dev --target_dir=substrate --features=riscv --pallet=pallet_revive
@mordamax Command |
Why are those flaky tests required again? It is really starting to get annoying. |