Skip to content

Latest commit

 

History

History
22 lines (19 loc) · 1.33 KB

File metadata and controls

22 lines (19 loc) · 1.33 KB

Stateless (zkEVM) Amsterdam+ EF tests skipped

Where: tooling/ef_tests/blockchain/test_runner.rsparse_and_execute skips fixtures with network >= Fork::Amsterdam when running with a stateless backend. Affects make test-stateless (the vectors_zkevm/ run); make test-levm is unaffected.

Why: The stateless run uses the tests-zkevm@v0.5.0 bundle, filled against glamsterdam-devnet v6.1.0, which predeploys the EIP-8282 builder deposit/exit contracts at the OLD addresses (0x0000884d…d9008282 / 0x000014574a…0f008282). This client uses the devnet-7 addresses (0x0000bff4…300d8282 / 0x000064d6…800e8282, matching the live tests-glamsterdam-devnet@v7.2.0 bundle used by make test-levm). Every Amsterdam+ block runs the end-of-block EIP-8282 builder system call; with the new addresses absent from the v0.5.0 bundle, each stateless Amsterdam+ block fails with SystemContractCallFailed("System contract: 0x0000…8282 has no code after deployment"). The skip is by fork rather than by test name, since cross-fork directories such as for_amsterdam/prague/... still execute at the Amsterdam fork.

Removal: Delete the skip_stateless_amsterdam branch in parse_and_execute once a tests-zkevm bundle filled with the devnet-7 builder predeploy addresses is released and .fixtures_url_zkevm is bumped to it.