-
Notifications
You must be signed in to change notification settings - Fork 799
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
Frame-omni-bencher weights are worse than old bench #6797
Frame-omni-bencher weights are worse than old bench #6797
Comments
@kianenigma @ggwpez ^^ pinging here |
I'll look into this |
@iulianbarbu try to change the following line: polkadot-sdk/.github/workflows/cmd.yml Line 367 in 89b0228
to:
|
@iulianbarbu note that to test this workflow change can be done through paritytech-stg, as this event trigger takes always workflow from master, so it's easier to test from there |
Was this closed by accident or do we know that this was the issue? |
@ggwpez yes, by accident as PR was merged, it auto-closed issue, thanks |
Latest test here, which used @bkchr 's suggested fix, ran against corresponding 9edaef0 on paritytech/polkadot-sdk/master, resulted in a smaller difference than what was shown initially in the issue description. My previous test which resulted in similar numbers as @mordamax showed in the issue description was done against: 350a6c4, which is not much different from 9edaef0 (as in nothing happened in between based on my understanding, that would impact pallet_balances weights on westend). I would conclude that @bkchr 's fix resolves the issue. Will follow up with the same change on |
# Description This PR builds frame-omni-bencher with `production` profile when calling `/cmd bench-omni` to compute benchmarks for pallets. Fix proposed by @bkchr , thanks! Closes #6797. ## Integration N/A ## Review Notes More info on #6797, and related to how the fix was tested: #6797 (comment). --------- Signed-off-by: Iulian Barbu <[email protected]> Co-authored-by: command-bot <>
a6ce732
This diff shows
the environment is the same (Github runner)
The text was updated successfully, but these errors were encountered: