-
Notifications
You must be signed in to change notification settings - Fork 54
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
Fix: benchmarking for pallet-data-preservers and pallet-registrar on Dancelight #783
Conversation
WASM runtime size check:Compared to target branchdancebox runtime: 1416 KB (no changes) ✅ flashbox runtime: 824 KB (no changes) ✅ dancelight runtime: 2152 KB (no changes) ✅ container chain template simple runtime: 1124 KB (no changes) ✅ container chain template frontier runtime: 1400 KB (no changes) ✅ |
Coverage Report@@ Coverage Diff @@
## master aleks-fix-data-preservers-benchmarking +/- ##
==========================================================================
- Coverage 65.24% 65.15% -0.09%
+ Files 329 330 +1
+ Lines 57701 57796 +95
==========================================================================
+ Hits 37646 37655 +9
+ Misses 20055 20141 +86
|
…egistrar and removed DataPreserversBenchmarkHelper
# Conflicts: # chains/orchestrator-relays/runtime/dancelight/src/weights/pallet_data_preservers.rs
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.
Thanks!
This PR adds benchmarking weights for
pallet-data-preservers
andpallet-registrar
to Dancelight.Changes:
RegistrarHandler
which reservesParaId
on Dancelight.ParaId
in failing benchmarking cases - Any value lower than 2000 will be overwritten by the currentLOWEST_PUBLIC_ID
defined in Polkadot SDK and the benchmarks will still fail after reserving aParaId