Files

1.5 KiB

Stopped run 1: nested TMPDIR exceeds the socket bound

Claim rev 3400, grant sage-3130/sage-3133. Started at load 3.57 on HEAD 57862d614, manifest cdda41f5. Controls and all four traced whole files ran; the broader seat and CLI suites did not start. No retry or candidate edit. Slot returned in gander-0175, final scratch cwd sweep zero.

First failure: lifecycle.test.mjs:261 expected null, got launch-failed; final whole-file count 13 pass, 11 fail. The trace records root /mnt/storage/scratch/tmp/g349BNE/proof-lifecycle.test/tmp/mosaic-life-CESgfT. newRun at session.mjs:278 refuses a tools.sock path above 107 bytes. This root plus /data/launches/acme/r123456789012/tools.sock is 120 bytes. launcher.mjs:472 calls newRun, and its exception becomes launch-failed. Static diagnosis, no diagnostic run.

Proposed harness correction: fresh TMPDIR directly under /mnt/storage/scratch/tmp/gXXXXXX, while logs and traces stay separate. The same socket path is 95 bytes. Candidate source and assertions remain unchanged. Filbert concurred from source at 02:34:08Z; placement remains with Sage/Mos. No correction or further run before placement/CLEAR.

The event JSONL files concatenate the unedited per-process event files. TRACE-INDEX.json records each original filename, byte offset, size and sha256, permitting exact reconstruction. Full raw per-process files also remain in the scratch directories recorded by the command files. The shim itself remains scratch-only; the controller source and actual control program are preserved here as evidence, not installed tooling.