70+ testsuite/ files across controller/scheduler/lib call mkdtemp() directly with no shared fixture helper, and none clean up after themselves. Left unchecked this fills the sandbox disk (recurred three times now: 2026-06-22, 2026-08-26, 2026-08-30, each larger than the last -- 696GB at its worst), which then surfaces as unrelated "Expected Non-NULL"-style cascade failures wherever the next test happens to call mkdtemp()/persist_init(), easily mistaken for a real regression. Retrofitting cleanup into 70+ individual test files would be invasive and risks breaking tests that inspect a fixture's contents across multiple TEST_ functions in the same file. Every test run in this project goes through xce-build.sh, so pruning once there -- age-gated at 3 hours so a concurrent session's in-progress fixtures are never touched -- is the lowest-risk single choke point. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019QxaSzHRB7pmYFp4cVnwkA |
||
|---|---|---|
| .. | ||
| appimage | ||
| deploy-ha.sh | ||
| go_build | ||
| test-build-version-regression.sh | ||
| test-commit-durability.sh | ||
| test-dirty-fingerprint-distinguishability.sh | ||
| test-dirty-fingerprint-nix-production-path.sh | ||
| test-dirty-fingerprint-startup-log-unchanged.sh | ||
| test-heartbeat-tolerance.sh | ||
| test-version-startup-consistency.sh | ||
| test-xceadmin-build-install-version.sh | ||
| xce-build.sh | ||