The Hive EEST glamsterdam-devnet shard sees this test fail intermittently in the merge queue. In the 24h window before #21361 it failed in 9 of 14 failing merge-group runs (and didn't appear in any passing run).

Test

tests/amsterdam/eip7954_increase_max_contract_size/test_max_initcode_size::test_max_initcode_size[fork_Amsterdam-blockchain_test_engine_from_state_test-over_max]

Failure mode (consistent whenever it does fail)

Undefined exception message:
  expected exception: "TransactionException.INITCODE_SIZE_EXCEEDED"
  returned exception: "previously known bad block"
  (mapper: "ErigonExceptionMapper")

The deterministic error string suggests the issue is in how erigon classifies the rejected block on the second presentation — it goes down the "previously known bad block" path rather than mapping back to the original INITCODE_SIZE_EXCEEDED reason that the test fixture expects. Single parametrization (over_max) is affected; other parametrizations of the same test pass.

Why this is open

#21361 raised max-failures for the shard from 2 → 4 so the merge queue tolerates this on top of the existing 2 known-tolerated baseline failures and the companion flake tracked in #21364. This issue tracks the actual fix; when both this and #21364 are resolved we ratchet max-failures back down.

Example failing jobs

• https://github.com/erigontech/erigon/actions/runs/26272726638/job/77329716379
• https://github.com/erigontech/erigon/actions/runs/26271470962/job/77325699790
• https://github.com/erigontech/erigon/actions/runs/26233342007/job/77199556910

Acceptance

• Test passes consistently across consecutive glamsterdam-devnet shard runs
• max-failures in .github/workflows/test-hive-eest.yml is lowered once both flakes are fixed