ci(test): reclaim ubuntu runner disk + drop test debug-info#295
Merged
Conversation
Ubuntu CI was hitting os error 28 (No space left on device) at link time — 14 tree-sitter parsers × 30+ test binaries × default debug-info filled the runner's 14 GB free space (last seen on PR #291 run 26240379100, tantivy.rlib link failed mid-cascade with callmeta_c_cpp misreported as the failing test). Two stacked mitigations: 1. Ubuntu-only `jlumbroso/free-disk-space` step before checkout — drops tool-cache + android + dotnet + haskell, reclaiming ~30 GB. macOS & windows have 50+ GB free by default; skipped there. 2. Job-level `CARGO_PROFILE_TEST_DEBUG=0` — shrinks target/debug/deps/ roughly 70%. Assertions stay on; only DWARF data is dropped.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
PR #291 (T4-7 MirrorsField) hit a misleading CI failure on
ubuntu-latest(run 26240379100):
Root cause: runner disk exhaustion, not a code bug. macOS test passed,
clippy/audit passed. The "test callmeta_c_cpp" line is a cascading cargo
report — the actual linker failure was
os error 28.The math: 14 tree-sitter parsers × ~30 test binaries × default debug-info
(
true) ≈ 30 GB intarget/debug/deps/. Default ubuntu runner free diskis ~14 GB. Inevitable as the workspace grew.
What
Two stacked mitigations, both ubuntu-targeted but the env var applies to
all OSes since it's harmless elsewhere:
jlumbroso/free-disk-spacestep before checkout (ubuntu-only)reclaims ~30 GB by dropping tool-cache + android SDK + dotnet + haskell.
large-packagesleft off — adds ~5 min for ~1 GB.swap-storageoff —risky if any step needs swap. Action pinned to v1.3.1 SHA per repo
convention (matches
step-security/harden-runner,actions/checkout).CARGO_PROFILE_TEST_DEBUG=0drops DWARF symbols fromtest binaries (~70 % size reduction). Assertions and overflow checks
stay on; only stack-trace symbolication is lost —
cargo nextestoutput already includes test names + file:line via panic hooks, so
diagnostic value is preserved.
Combined: ~14 GB baseline + ~30 GB reclaimed − ~9 GB build ≈ ~35 GB
buffer. Future language / dependency growth has headroom.
Test plan
Run tests (nextest)Test on ubuntu-latestjob →expect green
Notes
reduces resource pressure when the test job does run.