-
Notifications
You must be signed in to change notification settings - Fork 19
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: update benchmark command #1631
Conversation
⏳ Running benchmarks and calculating weights. DO NOT MERGE! A new commit will be added upon completion... |
additional reference: paritytech/substrate#11637 |
✅ Finished running benchmarks. Updated weights have been committed to this PR branch in commit 2907038. |
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.
Do we need to update the spec_version
just because weights were updated? Otherwise lgtm.
Yes, after the weights were updated, the metadata-mismatch test triggered. |
# Goal The goal of this PR is to update the benchmark command with an additional argument `--additional-trie-layers=20`. Closes #1630 # Discussion Due to changes in Polkadot v0.9.38, it is recommended to update the benchmark command. # Checklist - [x] Chain spec updated - [ ] Custom RPC OR Runtime API added/changed? Updated js/api-augment. - [ ] Design doc(s) updated - [ ] Tests added - [ ] Benchmarks added - [x] Weights updated --------- Co-authored-by: Frequency CI [bot] <do-not-reply@users.noreply.github.com>
Goal
The goal of this PR is to update the benchmark command with an additional argument
--additional-trie-layers=20
.Closes #1630
Discussion
Due to changes in Polkadot v0.9.38, it is recommended to update the benchmark command.
Checklist