From 49287746507b32225afad446cfb2c55220246ef6 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 8 Oct 2026 21:48:44 +0200 Subject: [PATCH] Point R335 at the merge of its fix, mesh-controller 8170fc5 --- replays/register.go | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/replays/register.go b/replays/register.go index eb6ed1a..2359530 100644 --- a/replays/register.go +++ b/replays/register.go @@ -234,9 +234,9 @@ var Register = []Replay{ // 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: "81e5458", Before: "ca09a07", + // own words, and put back. A test in the controller, written with only what it had before the fix, laid + // over the commit before. Fix is the merge of the fix. + {ID: "R335", Issue: 335, Kind: InRepository, Repository: "mesh-controller", Fix: "8170fc5", 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, " +