-
Notifications
You must be signed in to change notification settings - Fork 739
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
Upgrade Proxy and Multisig pallets to Benchmarking V2 #6018
Upgrade Proxy and Multisig pallets to Benchmarking V2 #6018
Conversation
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.
Looks like a few things need to be tidied up - make sure you're passing --features=runtime-benchmarks
when you check
Co-authored-by: Dónal Murray <[email protected]>
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.
CI needs to pass, but looks good otherwise.
Review required! Latest push from author must always be reviewed |
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.
Thank you!
Last question:
Please check the rust-doc of the each macro respectively, and see if the docs are sufficient and/or can be improved? Some ideas
- Does the v1 one mention the existence of v2?
- Is there a good "migration" guide available or noted anywhere?
If CI checks are not relevant, we can merge this anyways, as the target branch is not master.
…hmarking-pallets-pm
253ce3f
into
kiz-frame-umbrella-in-pallets
# Adding instruction to migrate benchmarking from v1 to v2 Even if the documentation for benchmarking v1 and v2 is clear and detailed, I feel that adding a migration guide from v1 to v2 would help doing it quicker. ## Integration This change only affects documentation, so it does not cause integration issues. ## Review Notes I followed the migration procedure I applied in PR #6018 . I added everything from there, but I may be missing some extra steps that are needed in specific case, so in case you notice something please let me know. --------- Co-authored-by: Dónal Murray <[email protected]>
Sub-task of PR #5995
Integration
These changes should not require any integration effort.