🤖 CI: pin geth to master-e5c5e18 in genesis-sync tests - #9605
Closed
dapplion wants to merge 1 commit into
Closed
Conversation
The gloas genesis-sync test started failing on `unstable` without any
related code change. The `ethpandaops/geth:master` nightly used by the
genesis-sync configs floated from the 2026-07-06 build (`e5c5e18`) to the
2026-07-09 build (`896a4ab`), and the newer build makes the Lighthouse
beacon node fail at startup on a gloas genesis with:
CRIT Failed to start beacon node
reason: "Failed to build beacon chain: Head block not found in store"
The last green run (07-07) used geth `e5c5e18`; the first red run (07-09)
used `896a4ab`. Fulu was unaffected but used the same floating tag, so pin
both genesis-sync configs to the last known-good geth build to stabilise CI.
dapplion
changed the title
master-e5c5e18 in genesis-sync testsmaster-e5c5e18 in genesis-sync tests
Member
|
Bad robot. Issue is with ethereum-genesis-generator |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue Addressed
The
genesis-sync-test-gloas-*jobs on thelocal testnetworkflow are failing onunstablewithout any related code change (e.g. seen on #9597). Thegenesis-sync-test-fulu-*jobs then get cancelled by fail-fast, so all four genesis-sync jobs show red.Root cause
The genesis-sync kurtosis configs use the floating
ethpandaops/geth:masternightly tag. That tag advanced from the2026-07-06build (e5c5e18) to the2026-07-09build (896a4ab), and the newer geth build makes the Lighthouse beacon node fail at startup on a gloas genesis:Kurtosis then can't bring up
cl-1-lighthouse-geth(ports never open) and the test exits 1. Fulu genesis is unaffected.Evidence it's the geth bump and not a Lighthouse change:
v1.17.5-unstable-e5c5e18-20260706v1.17.5-unstable-896a4ab-20260709Proposed Changes
Pin both genesis-sync configs (
fuluandgloas) to the last known-good geth buildethpandaops/geth:master-e5c5e18to stabilise CI. Thegloasconfig previously specified no EL image and inherited the floating default; it now pins geth explicitly like thefuluconfig.This is a CI-stabilisation pin only. Whether the newer geth build is itself buggy or exposes a latent gloas-genesis fragility in Lighthouse is a separate investigation; this unblocks the merge queue in the meantime.