execution/engineapi: TestEngineApiReorgWithPruningInterference fails again: poke submission did not settle

Open
#26,032 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go

Research direction

Start with engine_api_state_churn_reorg_test.go, especially the submission retry around line 304, and inspect the linked CI failures and earlier reports #23377 and #23540 for context. Reproduce the test and trace why poke submissions encounter nonce-gap and already-known errors without settling. Done when the test reliably passes under pruning interference and the reported CI failure no longer recurs.

Written by the indexing model from the issue text.

Description

flaky test
  • Failed in sonar / sonar on two merge-queue runs; both PRs re-entered the queue unchanged
    • 2026-10-13, #24706: job
    • 2026-10-16, #23030: job
  • The 2026-10-16 failure is after #24849 (fix for #23540, merged 2026-10-14); earlier report: #23377
  • No later commit on main names the test; engine_api_state_churn_reorg_test.go last changed in #23818 on 2026-09-10
engine_api_state_churn_reorg_test.go:304: poke 0 submission retry: INTERNAL_ERROR: nonce gap too large: transaction nonce is too far ahead of sender's on-chain nonce
engine_api_state_churn_reorg_test.go:304: poke 0 submission retry: ALREADY_EXISTS: already known
engine_api_state_churn_reorg_test.go:300:
    Error:      Condition never satisfied
    Messages:   poke submission did not settle
Dominant language
Go
Stars
3.6k
Forks
1.6k
Avg merge
1d 17h
Merged PRs (30d)
820

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from erigontech/erigon

All issues in erigontech/erigon

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.