-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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.
The new weights are very constistant with the previous 0.9.26-1
release.
@@ -89,11 +89,11 @@ impl<T: frame_system::Config> pallet_election_provider_multi_phase::WeightInfo f | |||
/// The range of component `v` is `[1000, 2000]`. | |||
/// The range of component `t` is `[500, 1000]`. | |||
fn create_snapshot_internal(v: u32, t: u32, ) -> Weight { | |||
(21_636_000 as Weight) | |||
(0 as Weight) |
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.
Down to 0
(0 as Weight) | ||
// Standard Error: 36_000 | ||
.saturating_add((24_281_000 as Weight).saturating_mul(s as Weight)) | ||
(908_000 as Weight) |
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.
0 to 900k
(1_851_000 as Weight) | ||
// Standard Error: 29_000 | ||
.saturating_add((23_826_000 as Weight).saturating_mul(s as Weight)) | ||
(0 as Weight) |
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.
down to 0
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.
Link to SWC staging (since Im testing some stuff).
Extrinsic and Block weights look good.
error[E0046]: not all trait items implemented, missing: |
.saturating_add(T::DbWeight::get().reads(5 as Weight)) | ||
.saturating_add(T::DbWeight::get().writes(5 as Weight)) | ||
} | ||
// Storage: PhragmenElection RunnersUp (r:1 w:0) | ||
fn remove_member_wrong_refund() -> Weight { |
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.
huh, this got dropped, breaking the build. i'll undo this change
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.
Yep not your fault, caused by paritytech/substrate#11790 which removed the benchmark but did not update the weight-trait.
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.
@ggwpez should i merge your pr into this branch to fix it rather than readding the old weight?
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.
It would be probably slightly cleaner to remove it from the trait as in my MR for Polkadot and Kusama.
This only makes a difference if someone re-benchmarks on this branch.
test failures: |
this is the one we already fixed last time, isn't it |
Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
test-linux-stable has some unrelated nonfatal errors in the test execution:
This is not our fault though and should probably be fixed by whoever maintains the test ci |
also |
bot merge |
Waiting for commit status. |
Merge cancelled due to error. Error: You're not authorized to push to this branch. Visit https://docs.github.com/articles/about-protected-branches/ for more information. |
bot merge |
Error: You're not authorized to push to this branch. Visit https://docs.github.com/articles/about-protected-branches/ for more information. |
weights from the 0.9.27 release benchmarks 🏋️♀️
Backport to master: #5844
cumulus companion branch: test-release-v0.9.27