-
Notifications
You must be signed in to change notification settings - Fork 402
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
Problems running multi_parachains.toml configuration using zombienet #1415
Comments
I'd suggest to check the content of the output file:
You can try & execute the steps to construct the chain spec manually (repeat the commands in your terminal, and observe the error you get). |
I tried executing the command manually as you suggested. Unfortunately, the result is the same. The file To investigate further, I added the
Despite the additional logs, I am still unable to generate the chain specification manually. After some testing, I noticed that if I commented out the specification of the second channel in the [settings]
timeout = 1000
node_verifier = "None"
# Used to start 4 validator nodes and 2 collator nodes - 1 per parachain
[relaychain]
#default_image = "paritypr/polkadot-debug:master"
default_command = "./bin/polkadot"
default_args = [ "-l=parachain=debug,xcm=trace" ]
chain = "rococo-local"
[[relaychain.nodes]]
name = "alice"
validator = true
[[relaychain.nodes]]
name = "bob"
validator = true
[[relaychain.nodes]]
name = "charlie"
validator = true
[[relaychain.nodes]]
name = "dave"
validator = true
[[parachains]]
id = 1000
# Replace this with whichever chain you need to run, e.g. `astar-dev` if you need Astar
chain = "shibuya-dev"
cumulus_based = true
[[parachains.collators]]
name = "collator1"
command = "../../../Astar/target/production/astar-collator"
rpc_port = 8545
args = [ "-l=xcm=trace", "--enable-evm-rpc" ]
# For this one you can download or build some other para and run it.
# In this example, `astar-collator` is reused but `shiden-dev` chain is used
[[parachains]]
id = 2007
chain = "shiden-dev"
cumulus_based = true
[[parachains.collators]]
name = "collator2"
command = "../../../Astar/target/production/astar-collator"
args = [ "-l=xcm=trace", "--enable-evm-rpc" ]
[[hrmp_channels]]
sender = 2000
recipient = 2007
max_capacity = 8
max_message_size = 8000
#[[hrmp_channels]]
# sender = 2007
# recipient = 2000
# max_capacity = 8
# max_message_size = 8000 I hope this additional information helps. |
If manual execution failed, then something is wrong with your polkadot binary. For the HRMP channel issue, there was (or still is?) a race condition when 2 HRMP clients are defined. |
Found the issue: paritytech/polkadot-sdk#1616 |
Description
I am encountering issues when trying to run
zombienet
with themulti_parachains.toml
configuration file located in./third-party/zombienet
.The problem occurs in both this two scenarios:
multi_parachains.toml
multi_parachains.toml
. This version was compiled using a MacBookPro arm64 version.with the following error
Steps to Reproduce
Expected
• The configuration file
multi_parachains.toml
should execute successfully without errors.• The
zombienet
command should generate througthpolkadot
the relay chain specifications (rococo-local) without any issues.•
zombienet
should initialize the parachains with evm envinroment and xcm support with preconfigured channelsEnvironment
rustup show
):Default host: aarch64-apple-darwin rustup home: /Users/francesco/.rustup installed toolchains -------------------- stable-aarch64-apple-darwin (default) nightly-aarch64-apple-darwin 1.77.0-aarch64-apple-darwin installed targets for active toolchain -------------------------------------- aarch64-apple-darwin wasm32-unknown-unknown active toolchain ---------------- stable-aarch64-apple-darwin (default) rustc 1.84.0 (9fc6b4312 2025-01-07)
Logs, Errors
The text was updated successfully, but these errors were encountered: