ci(standards-build): build jouleclaw-rs on linux-arm64 without debuginfo #95
2026-09-17
ci(standards-build): build jouleclaw-rs on linux-arm64 without debuginfo
All checks were successful
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m49s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m18s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m10s
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 5m20s
standards workspaces build + test / aac-rs (pull_request) Successful in 50s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m7s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 1m27s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 2m31s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 1m45s
standards workspaces build + test / map-rs (pull_request) Successful in 1m1s
standards workspaces build + test / mesh-rs (pull_request) Successful in 1m24s
standards workspaces build + test / openpay (pull_request) Successful in 2m22s
standards workspaces build + test / arl-rs (pull_request) Successful in 2m5s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 2m18s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 11m37s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 12m3s
standards workspaces build + test / sense-rs (pull_request) Successful in 2m27s
The jouleclaw-rs leg on linux-arm64 has been red on main because its aarch64 test target, with Linux's full DWARF embedded in every test binary, outgrows the ~15 GB left on the shared txarm volume (/var/lib/docker and /ci-cache are both on /dev/vdb1, 87% used). The link fails with "No space left on device" — a capacity failure, not a code failure. Reproduced with the same toolchain, +fp16 rustflags and image: with debuginfo the build runs out of space at link; with CARGO_PROFILE_DEV_DEBUG=0 the target is ~6 GB and the full suite passes. Scoped to this one job via $GITHUB_ENV (a matrix-level env field would give every other job an empty CARGO_PROFILE_DEV_DEBUG). A cache_suffix moves this job to a fresh cache namespace so it cannot restore the old full-debuginfo target alongside the new build; every other job's cache key string is unchanged. Co-Authored-By: Claude Opus 5 <[email protected]>