Skip to content

Auto-update of all weights for 2025-01-25-1737769694#7337

Closed
paritytech-cmd-bot-polkadot-sdk[bot] wants to merge 1 commit intomasterfrom
update-weights-weekly-2025-01-25-1737769694
Closed

Auto-update of all weights for 2025-01-25-1737769694#7337
paritytech-cmd-bot-polkadot-sdk[bot] wants to merge 1 commit intomasterfrom
update-weights-weekly-2025-01-25-1737769694

Conversation

@paritytech-cmd-bot-polkadot-sdk
Copy link
Copy Markdown
Contributor

Auto-update of all weights for 2025-01-25-1737769694

@paritytech-cmd-bot-polkadot-sdk paritytech-cmd-bot-polkadot-sdk bot added the R0-no-crate-publish-required The change does not require any crates to be re-published. label Jan 25, 2025
@paritytech-cmd-bot-polkadot-sdk paritytech-cmd-bot-polkadot-sdk bot requested review from a team January 25, 2025 01:48
@paritytech-workflow-stopper
Copy link
Copy Markdown

All GitHub workflows were cancelled due to failure one of the required jobs.
Failed workflow url: https://github.com/paritytech/polkadot-sdk/actions/runs/12960658092
Failed job name: build-runtimes-polkavm

@paritytech-workflow-stopper
Copy link
Copy Markdown

All GitHub workflows were cancelled due to failure one of the required jobs.
Failed workflow url: https://github.com/paritytech/polkadot-sdk/actions/runs/12960658076
Failed job name: check-try-runtime

@gui1117
Copy link
Copy Markdown
Contributor

gui1117 commented Jan 28, 2025

I think the templates are using frame but not all crates have frame as a dependency. So it fails to compile.

Either we add frame as a dependency, to all concerned crates, or we revert the change in the template

@mordamax
Copy link
Copy Markdown
Contributor

mordamax commented Jan 28, 2025

@gui1117 the goal would be that next time it regenerates - it won't fail. if we revert a change in template, https://github.com/paritytech/polkadot-sdk/pull/6789/files#diff-5a2955b61af496005e95ef8d82448fcd76fd957fe4f382b1a757bdfaf0335dd4 then the multisig will be failing next time again?
or pallet_multisig should've used other template based on umbrella crate https://github.com/paritytech/polkadot-sdk/blob/master/.github/scripts/cmd/cmd.py#L227? I wonder may be the dependencies of the multisig_pallet should've fixed instead so it picks up the right template instead of fixing the old templaet

@gui1117
Copy link
Copy Markdown
Contributor

gui1117 commented Jan 28, 2025

I see.
Looking again, what I see failing is frame-system, because the dependency frame doesn't exist. But frame-system should better not depend on frame to avoid a cyclic dependency.

And the template substrate/.maintain/frame-weight-template.hbs is using frame.

system should not use frame.

Is there a reason substrate/.maintain/frame-weight-template.hbs is using frame and not frame-support.
EDIT: yes it seems multisig_pallet should be fixed and we shouldn't change the old template

@kianenigma
Copy link
Copy Markdown
Contributor

The weight generation script should inspect the crate, and make a decision about the template based on:

  1. if frame is a dependency
  2. if not.

I have not seen the PR, but this should work in practice. @gui1117 does this make sense?

@mordamax
Copy link
Copy Markdown
Contributor

Here's a PR fixing a template issue #7362
I will re-start generation all pallets once ☝️ merged

@mordamax mordamax closed this Jan 28, 2025
@gui1117
Copy link
Copy Markdown
Contributor

gui1117 commented Jan 29, 2025

The weight generation script should inspect the crate, and make a decision about the template based on:

1. if `frame` is a dependency

2. if not.

I have not seen the PR, but this should work in practice. @gui1117 does this make sense?

Yes, the template were changed to always use frame in both cases. This should be now fixed. we will see if there is any error remaining.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

R0-no-crate-publish-required The change does not require any crates to be re-published.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants