Skip to content

Conversation

moliholy
Copy link
Contributor

This PR improves the zombienet script by directly downloading the corresponding polkadot binaries instead of building them from source.

@moliholy moliholy requested a review from metricaez April 10, 2025 10:51
@moliholy moliholy self-assigned this Apr 10, 2025
@moliholy moliholy force-pushed the refactor/zombienet-improvements branch from 612897c to c52dbd6 Compare April 10, 2025 10:51
@metricaez
Copy link
Collaborator

Not getting past a new era with block producing, neither with testnet or mainnet (paseo or polka relay) profiles. Config should be reviewed.

@moliholy moliholy marked this pull request as draft April 10, 2025 15:05
@moliholy
Copy link
Contributor Author

Converting to draft until we find out what's going on when initializing the relay chain and onboarding parachains.

2025-04-10 16:39:12.011  WARN tokio-runtime-worker runtime::inclusion-inherent: Processing inherent data failed: <wasm:stripped>
2025-04-10 16:39:12.011 ERROR tokio-runtime-worker runtime: panicked at /Users/molina/.cargo/git/checkouts/polkadot-sdk-dee0edd6eefa0594/b6a646d/polkadot/runtime/parachains/src/paras_inherent/mod.rs:208:5:
Bitfields and heads must be included every block
2025-04-10 16:39:12.012  WARN tokio-runtime-worker babe: Proposing failed: Import failed: Error at calling runtime api: Execution failed: Execution aborted due to trap: wasm trap: wasm `unreachable` instruction executed
WASM backtrace:
error while executing at wasm backtrace:
    0: 0x7248bc - paseo_runtime.wasm!rust_begin_unwind
    1: 0xf78d - paseo_runtime.wasm!core::panicking::panic_fmt::hcbb12cbae8ad4653
    2: 0x66cb1f - paseo_runtime.wasm!<(TupleElement0,TupleElement1,TupleElement2,TupleElement3,TupleElement4,TupleElement5,TupleElement6,TupleElement7,TupleElement8,TupleElement9,TupleElement10,TupleElement11,TupleElement12,TupleElement13,TupleElement14,TupleElement15,TupleElement16,TupleElement17,TupleElement18,TupleElement19,TupleElement20,TupleElement21,TupleElement22,TupleElement23,TupleElement24,TupleElement25,TupleElement26,TupleElement27,TupleElement28,TupleElement29,TupleElement30,TupleElement31,TupleElement32,TupleElement33,TupleElement34,TupleElement35,TupleElement36,TupleElement37,TupleElement38,TupleElement39,TupleElement40,TupleElement41,TupleElement42,TupleElement43,TupleElement44,TupleElement45,TupleElement46,TupleElement47,TupleElement48,TupleElement49,TupleElement50,TupleElement51,TupleElement52,TupleElement53,TupleElement54,TupleElement55,TupleElement56,TupleElement57,TupleElement58,TupleElement59,TupleElement60,TupleElement61) as frame_support::traits::hooks::OnFinalize<BlockNumber>>::on_finalize::h3efe35aa7b631bc3
    3: 0x19bf8e - paseo_runtime.wasm!frame_executive::Executive<System,Block,Context,UnsignedValidator,AllPalletsWithSystem,COnRuntimeUpgrade>::finalize_block::hc870bf5b5ae7ade6
    4: 0x27477b - paseo_runtime.wasm!BlockBuilder_finalize_block

@alexggh
Copy link
Contributor

alexggh commented Jun 30, 2025

Converting to draft until we find out what's going on when initializing the relay chain and onboarding parachains.

2025-04-10 16:39:12.011  WARN tokio-runtime-worker runtime::inclusion-inherent: Processing inherent data failed: <wasm:stripped>
2025-04-10 16:39:12.011 ERROR tokio-runtime-worker runtime: panicked at /Users/molina/.cargo/git/checkouts/polkadot-sdk-dee0edd6eefa0594/b6a646d/polkadot/runtime/parachains/src/paras_inherent/mod.rs:208:5:
Bitfields and heads must be included every block
2025-04-10 16:39:12.012  WARN tokio-runtime-worker babe: Proposing failed: Import failed: Error at calling runtime api: Execution failed: Execution aborted due to trap: wasm trap: wasm `unreachable` instruction executed
WASM backtrace:
error while executing at wasm backtrace:
    0: 0x7248bc - paseo_runtime.wasm!rust_begin_unwind
    1: 0xf78d - paseo_runtime.wasm!core::panicking::panic_fmt::hcbb12cbae8ad4653
    2: 0x66cb1f - paseo_runtime.wasm!<(TupleElement0,TupleElement1,TupleElement2,TupleElement3,TupleElement4,TupleElement5,TupleElement6,TupleElement7,TupleElement8,TupleElement9,TupleElement10,TupleElement11,TupleElement12,TupleElement13,TupleElement14,TupleElement15,TupleElement16,TupleElement17,TupleElement18,TupleElement19,TupleElement20,TupleElement21,TupleElement22,TupleElement23,TupleElement24,TupleElement25,TupleElement26,TupleElement27,TupleElement28,TupleElement29,TupleElement30,TupleElement31,TupleElement32,TupleElement33,TupleElement34,TupleElement35,TupleElement36,TupleElement37,TupleElement38,TupleElement39,TupleElement40,TupleElement41,TupleElement42,TupleElement43,TupleElement44,TupleElement45,TupleElement46,TupleElement47,TupleElement48,TupleElement49,TupleElement50,TupleElement51,TupleElement52,TupleElement53,TupleElement54,TupleElement55,TupleElement56,TupleElement57,TupleElement58,TupleElement59,TupleElement60,TupleElement61) as frame_support::traits::hooks::OnFinalize<BlockNumber>>::on_finalize::h3efe35aa7b631bc3
    3: 0x19bf8e - paseo_runtime.wasm!frame_executive::Executive<System,Block,Context,UnsignedValidator,AllPalletsWithSystem,COnRuntimeUpgrade>::finalize_block::hc870bf5b5ae7ade6
    4: 0x27477b - paseo_runtime.wasm!BlockBuilder_finalize_block

Root cause of the problem: #308 (comment).

TLDR a newer paseo relay runtime 1.5 or newer should work.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants