Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Added support for coretime-kusama/polkadot and people-kusama/polkadot #3961
Added support for coretime-kusama/polkadot and people-kusama/polkadot #3961
Changes from 3 commits
2eec00d
2349ee0
778f385
d1e1a26
d20140d
9398a07
148ced8
515b31e
9aeabc9
c7dbfa8
a95bab8
39274bb
cff49c6
22f8f1a
35a7330
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Large diffs are not rendered by default.
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.
We should not include the local variants. If people need them, they need to create the chain specs themselves. Most of the time you want for the local variants any way the latest code.
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.
Don't the benchmark scripts use local?
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.
Well, I just remember @serban300's PR where he had to add this local variants to be able run fellows zombienet tests for BridgeHubKusama/BridgeHubPolkadot.
We don't provide chain-specs for local variants here as I explained bellow: #3961 (comment).
These local variants are needed for parsing
id
string from chain-spec and used for managing what kind of node to run here: https://github.com/paritytech/polkadot-sdk/pull/3961/files#diff-517780020940588a81c29ec543f6c5dff196c985641a28826c955ac35d1aa02bR761-R764I think,
polkadot-parachain-bin
should be maybe chain-agnostic and we should provide just chain-spec json file. So we should remove all these chain-specific stuff frompolkadot-parachain
and extract that to new cratechain-spec-generator
for testnets as we have for fellows.And also, for controlling what setup to run
start_generic_aura_node
vsstart_generic_aura_lookahead_node
vsstart_asset_hub_node
vsstart_asset_hub_lookahead_node
, we could add new command parameter (or maybe attribute to chain-spec?).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.
We can improve and refactor whatever way, but let's continue here #3944 or is there any other issue?
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.
I think you need just chain-spec for benchmarks, e.g for fellows benchmarks, I just needed
chain-spec-generator
to generate a local chain spec forcoretime-kusama-local
, and then usepolkadot
binary:I didn't try to run benchmarks with
polkadot-parachain
, anywayomni-bencher
is coming, so we won't even need chain-spec for benchmarking