From e143cc88eeb2146d79db48ce034e6cc25de858db Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 8 Oct 2026 20:26:39 +0200 Subject: [PATCH] Register R335, so a passed gate failed by later reports fails before a core merge hq issue 335: a build that passed its gate was failed and put back when the first machine's later reports went quiet. Proved: fails on 7f65e62, passes on becd40b. --- replays/register.go | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/replays/register.go b/replays/register.go index 5363b90..19851e4 100644 --- a/replays/register.go +++ b/replays/register.go @@ -231,6 +231,17 @@ var Register = []Replay{ Asserts: "a tool check on the NATS link the node-engine attaches reaches that link, and is not refused as no link", Package: "./internal/link", Test: "TestReplay331", Files: []string{"internal/link/replay331_test.go"}, Home: "mesh-host", HomeRef: "5684a4579d92"}, + // A passed build put back half an hour after its pass (2026-10-08): dunst passed its gate on the laptop, + // its send to the rest waited on another walk, that walk sent the laptop a declaration it did not report + // on, and the plan read the silence as the passed build never applied: failed at its gate with the pass's + // own words, and put back. A test in the controller, written with only what it had before the fix. The + // fix is still on its branch: Fix is its pull request's head, proved against the main it stands on. + {ID: "R335", Issue: 335, Kind: InRepository, Repository: "mesh-controller", Fix: "becd40b", Before: "7f65e62", + What: "a build that passed its gate on the laptop (healthy 3 times over 2m5s) was marked failed at its " + + "gate 28 minutes later, with those words as the reason, and put back", + Asserts: "once a build passed its gate, the first machine's later reports neither fail it nor hold the rest, " + + "and a walk stopped after the pass keeps it", + Package: "./cmd/mesh-controller", Test: "TestReplay335", Files: []string{"cmd/mesh-controller/replay335_test.go"}}, // Not a core incident, and the first of its kind: a module's. The crash loop was found by a person // reading the agent server's log for another reason (issue 268); research 032 measured it, and ADR // 0240 makes the node-engine judge it and the gate fail it.