cargo-test-weekly failed twice today with exit 124 at unit 427/429 — the
non-incremental test-profile build running out of wall clock mid-compile,
before a single test executed. The summary said only "FAIL: cargo-test-
weekly", which reads as a broken test and sends you hunting for one that
does not exist.
Two changes: the ceiling goes 1500s -> 3600s (580s was already found too
short; 1500s now dies on the biggest link on a loaded, swapping box), and
stage() names exit 124 as a timeout rather than printing a bare code.
Verified both reporting branches: a timed-out stage and an ordinary
non-zero exit.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The ui-unit-tests stage piped vitest through `tail -4`, which cut off the
failure block. A red gate reported "1 failed | 999 passed" and nothing
else — no file, no test name, no assertion — so the failure could not be
diagnosed after the run.
Success still prints the quiet 4-line summary; failure now dumps the full
log and keeps it on disk so a scrolled-off terminal isn't the end of it.
Verified both paths: green run unchanged, and a deliberately failing spec
now surfaces its file, test name, assertion and line number.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
