stack/agents/gizmoduck/work/queue-292/RESULTS.md

Row 292 (#1797) gate results

Tested head: 0d00214545 (sage-3185). That's 3fd8f42f6 rebased onto c902a767d. It's on gizmoduck/row292-r2. The round 1 manifest digest is still 2fa7ae17 (13 paths). This file and RED-r2.md came after the gate and sit outside the manifest.

Rebase receipts (sage-3183 item 1)

git range-diff -s b23783f39..3fd8f42f6 c902a767d..0d0021454 shows all six commits as =:

1:  3b17c7550 = 1:  89e58f4b1
2:  a54baff21 = 2:  9f15216f7
3:  9c6e39b25 = 3:  61fdb6a8d
4:  4fa7d6834 = 4:  b48e415e4
5:  f8b9c2f73 = 5:  2db30c687
6:  3fd8f42f6 = 6:  0d0021454

Stable patch-ids are unchanged: 15f1a38e, 8e9b78ac (e7371025f), fc50b630 (d4c796e44), b5a6c8e8, d918d3cd, 9e2b2c2b. Every one of the 13 manifest blobs on 0d0021454 matches the manifest.

Gate r2 (04:33Z to 04:54Z 10-23, CLEAR sage-3183)

• stack-release.test.mjs whole: rc=0, 224/224, wall 608 s.
• cli suite whole: rc=1, 910 tests, 909 pass, 1 fail. The failure is in an old test, compactions-launch.test.mjs:206 (row 270's store-unreadable test), at :229 deepEqual(ends[0], ends[1]). ends[0] was ['session-invalid', 22, null] and ends[1] was ['stopped', 0, null]. Under mos-1272 the run stopped with the red unplaced. RED-r2.md has the reading: the idle stop releases the claim before it sends SIGTERM, so a poll in between gets not-holder and exits 22. Mos ruled in mos-1411 that :229 stays as written and the race gets its own row, Vikunja 588.

Diagnostic (mos-1411, CLEAR sage-3193)

05:01:01Z to 05:03:31Z: compactions-launch.test.mjs, whole and unedited, run 10 times, each with its own TMPDIR. All ten passed with rc=0 and 5/5, so ends[0] was stopped/0 every time. In the runner.logs, 72 end in exit 0, 27 were deleted before the copy loop reached their last line, and one ended session stopped working: not-holder then exiting 22. That one was run 2's launch r846b8d083502, in the clear test (:305), which doesn't compare ends. So the race happens and the code is not-holder.

Gate r3 (05:03:50Z to 05:16:32Z, run-gate-r3.sh)

• Stage 1 didn't rerun because it was green in r2.

• cli suite whole and unedited: rc=0, 910/910, 0 skipped, wall 630 s. Under mos-1411, this green rerun is what makes 292's gate count.

• The ten scripts/test-*.sh all passed with rc=0:

  Suite	Result
  auth	15/0
  conductor	17/0
  config	55/0
  discord	81/0
  extension-package	18/0
  foundation	44/0
  land-work	86/0
  queue	node 156/156, suite 28/0
  release	14/0
  task	91/0

  The tree was clean afterwards.

• There were two skips, both the usual ones. test-queue skipped verify/render --check because this checkout isn't the canonical root. test-task skipped the live provider cases (row 244). No Docker group was skipped.

• All of M1-M9 were killed by the rule: each had fail 1 on the named test, every listed stack line and the kill text. Each restore checked sha256 8f535d53 and found the tree clean. No survivors.

• When it finished, no node process had its cwd in the worktree.

Logs are in /mnt/storage/scratch/gizmo-292-out: r2.out, r2/, diag.out, diag/, r3.out and r3/.

For the landing note (mos-1411)

The first red was compactions-launch.test.mjs:229 in gate r2, with ends[0] ['session-invalid', 22, null]. The race is Vikunja 588. The gate counts on the green r3 cli rerun.