1.7 KiB
Full restart r5: sage-3313 / post-302 merge
Merged b899095e4 onto 07802dc57a, clean, merge 06d7cc2f0f.
Both row302 and row219 changes in broker.mjs and threads.test.mjs retained
by the automatic merge; no manual product/test edits. New 16-path manifest
420befed0aa8291736d34187ac7e745b7660efed15348ece045a7dd8957c9124.
No previous runs carried. All 10 whole touched files, bus/cli/webui/harness
suites, all shell files, 24 mutants, reader audit. Fresh short TMPDIR per
stage, process groups, timeout -k 10; previous time limits remain.
Packet runner now writes a fresh run-0780-mos1429 directory and includes
harness explicitly. It classifies GNU timeout exit 124/137 or signal -9 as
timeout too, so a timed-out mutant can never be called assertion-killed.
No mutation/test/product changes for that runner classification correction.
Every old-test red (including compactions-launch:229) stops for Mos.
Runner-only restart under mos-1432 / sage-3323
Previous full run stopped at harness claude-session.test.mjs:298. Saved
TMPDIR /mnt/storage/scratch/tmp/rh85v_4j3 contains underscore; the fixture's
slug replaces only / and . while Claude normalizes underscore too. Sage's
clean-base diagnostic reproduces 10/0 with alphanumeric TMPDIR and 9/1
with underscore. Latent test bug is a separate row; no code/test fix here.
Runner now creates each stage TMPDIR with mktemp -d
/mnt/storage/scratch/tmp/rXXXXXX and rejects any full path outside
[A-Za-z0-9/.-]. New output run-0780-mos1432 preserves the prior red logs.
Same merge 06d7cc2f0 and 16-path manifest 420befed; no results carried.
Full restart waits for Sage CLEAR after 295. No tests or Node in preparation.