docs(records): row 33 landed, cold-start failure reopened (#1508)
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
+14
-1
@@ -138,6 +138,18 @@ at every gate. Started 2026-09-12 during the control board MVP.
|
||||
Sage asked the SetSpark lead to use a one-word role. The rule stays as
|
||||
it is. (2026-09-26, #1506)
|
||||
|
||||
- **Queue tests: the cold-start failure came back (reopened).** Row 33
|
||||
closed this as not reproduced in 20 idle cold runs. On 2026-10-04 Sage's
|
||||
index export of the row 33 candidate ran the nine suites, then
|
||||
`node --test packages/queue/tests/`, and got 147 passed, 1 failed. Sage's
|
||||
recipe threw the output away, so again nobody knows which test failed.
|
||||
Ten more runs all passed 148/148: three reruns in the same export, four
|
||||
under parallel suite load, and three fresh exports run straight after
|
||||
`test-queue.sh`. It needs a first run on a fresh tree after a full
|
||||
suite pass, and even then it's rare. Darkwing's n2 on row 33 (the cold
|
||||
runs were idle) was right. Next time: Sage's export recipe keeps the
|
||||
node test output in a file, so the first failure has a name. Then fix it
|
||||
as its own row. (2026-10-04, #1508)
|
||||
- **Queue: `add --issue N` also sets closes to N.** Follow-up rows under
|
||||
an umbrella issue, like rows 31 and 33 under #1508, would close the issue
|
||||
when they finish. Sage narrowed both by hand (revs 36 and 43). Either
|
||||
@@ -180,7 +192,8 @@ Moved to `docs/plans/QUEUE.md` on 2026-09-13. This file holds only gaps.
|
||||
built it in the Gate G run, and Filbert approved round 1 (#1508 comment
|
||||
26629, 8 of 8 mutants caught).
|
||||
- Queue follow-ups from rows 12, 13 and 31 (2026-10-04, #1508): closed by
|
||||
row 33. Filbert built it, and Darkwing reviews it.
|
||||
row 33, 6fb50cc0. Filbert built it, and Darkwing approved round 1
|
||||
(#1508 comment 26651).
|
||||
- `genesis` refuses a map row whose owner is one of its reviewers (exit
|
||||
2, nothing written). The check is on the map, not in replay, so a log
|
||||
from before the rule still loads.
|
||||
|
||||
Reference in New Issue
Block a user