devnet-7: buildoor action-plan-rules canary on buildoor-lighthouse-geth-1 - #49
Merged
Merged
Conversation
This was referenced Jul 27, 2026
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
1 participant
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.
Runs the buildoor PR build with per-slot recurring action plan rules (ethpandaops/buildoor#147) on one builder only —
buildoor-lighthouse-geth-1. The other three buildoors stay ondefault_tooling_images.buildoor(main-latest).Why: a rule repeats a slot plan on the same slot index of every epoch, so "win slot 31 and withhold its payload" holds for a whole devnet run instead of a bounded slot list — the ePBS side of testing an epoch-boundary slot that produces no execution payload.
Behaviour on deploy: none. The rule set starts empty; the scenario is armed explicitly via the WebUI or
POST /api/buildoor/action-plan/rules. Rules live in the state-db (/data/buildoor.sqlite), so they survive container recreates and watchtower updates.Image
ethpandaops/buildoor:qu0b-action-plan-recurring-rules-latestis a moving tag on purpose: this host is in the watchtower list, so further pushes to the PR branch roll out here automatically.Revert: delete the file and re-run
--tags buildoor --limit buildoor-lighthouse-geth-1.