Point R335 at the merge of its fix, mesh-controller 8170fc5
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript), replays/merge-check.sh (go)
mesh/delivery superseded: a newer head of the same pull request

This commit is contained in:
jochen
2026-10-08 21:48:44 +02:00
parent d3161806d2
commit 4928774650
+3 -3
View File
@@ -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, " +