check-all sat on two lines of output for over an hour. The cause was the 5.1 bed
in check-capture-controls: ffmpeg completes the filter graph and then never exits.
Diagnosed rather than guessed -- the output reaches 4604262 bytes, exactly 8.0 s
of 5.1ch/16-bit/48kHz, the full intended length, with the artifact correct on disk
while the process hangs.
Three formulations all hang and all produce byte-identical output: the original,
one with -t 8 bounding the output, and one with explicit asplit feeding each atrim
(the textbook fix for multi-use of a single input). So it is not the split, not
the output stage, and the artifact is not in doubt.
Worse than the hang: it leaks. An orphaned ffmpeg from this script's earlier aloop
form was still running after 9.5 hours, burning CPU across runs nobody was
watching. boot.gd's header already names the shape -- a job that waits forever
reads as a job still working.
Bounded with timeout, and the ARTIFACT is now checked rather than the exit code:
the bed's duration must be 8 s or the sweep refuses to score itself. That is the
better test regardless of the hang -- an exit code says ffmpeg thought it was
done, the file says what it wrote. The step now completes in 99 s and the sweep
matches its specification.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
d613609aaf