Fix benchmarks after upgrade to stable 2409 #3158
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
manuelmauro
added
D3-trivial
WASM runtime size check:Compared to target branchMoonbase runtime: 2272 KB (-148 KB) ✅ Moonbeam runtime: 2252 KB (-152 KB) ✅ Moonriver runtime: 2244 KB (-156 KB) ✅ Compared to latest release (runtime-3401)Moonbase runtime: 2272 KB (+240 KB compared to latest release) Moonbeam runtime: 2252 KB (+240 KB compared to latest release) Moonriver runtime: 2244 KB (+232 KB compared to latest release) |
manuelmauro
added
the
B0-silent
Coverage Report@@ Coverage Diff @@
## master manuel/fix-benchmarks-post-upgrade-stable2409 +/- ##
=================================================================================
- Coverage 74.59% 74.58% -0.01%
- Files 380 377 -3
+ Lines 96035 96042 +7
=================================================================================
Hits 71632 71632
+ Misses 24403 24410 +7
|
RomarQ
approved these changes
Jan 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does it do?
After upgrading to polkadot-sdk stable2409, some benchmarks are now failing. This PR fixes the broken benchmarks.
What important points reviewers should know?
Is there something left for follow-up PRs?
What alternative implementations were considered?
Are there relevant PRs or issues in other repositories (Substrate, Polkadot, Frontier, Cumulus)?
What value does it bring to the blockchain users?