ci(test): free runner disk space before the integration shard build (fixes ENOSPC on main)#6112
Merged
Merged
Conversation
…fixes ENOSPC on main) The `Test / Ubuntu (shard N/4)` job's full-run path runs `cargo test --workspace --no-run`, which debug-compiles every workspace test binary — each `tests/*.rs` is its own executable, plus dev-dependencies and librefang-desktop's large static archive — on an ubuntu-latest runner that leaves only ~14 GB free. All four full-run shards do this same heavy build, so the disk sits at the margin: shard 1/4 overran it on main and the runner died with "No space left on device" mid-build, before any test ran. Add a Free-runner-disk-space step (gated on the same selective-lane skip as the rest of the job) that removes preinstalled toolchains this job never uses — dotnet, Android SDK, GHC, CodeQL, docker images — reclaiming ~25 GB. This extends the same fix the unit-test job got in #6089 and nix-build got in #6081 to the integration shard lane, the last full-workspace Ubuntu build still exposed. Verified: ci.yml still parses as valid YAML.
github-actions
Bot
added
no-rust-required
houko
enabled auto-merge (squash)
June 15, 2026 04:16
Two-line comment block condensed to one short line per project style rules. The PR body carries the full context; inline comments reference only the non-obvious constraint (disk headroom).
github-actions
Bot
added
the
no-rust-required
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
2 participants
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.
Problem
Test / Ubuntu (shard 1/4)failed onmain(run 27518045628) with the runner annotation:This is not a test failure — the runner ran out of disk mid-build, before any test executed.
Root cause
The
test-ubuntuintegration shard job's full-run path runscargo test --workspace --no-run, which debug-compiles every workspace test binary (eachtests/*.rsis its own executable, plus dev-dependencies and librefang-desktop's large static archive).ubuntu-latestleaves only ~14 GB free, and all four full-run shards do this same heavy build, so the disk sits right at the margin — shard 1/4 tipped over it.This is the same class of failure that hit
Test / Unit (lib+bin)in #6089 andnix-buildin #6081. Both got a disk-free step; the integration shard lane — the last full-workspace Ubuntu build still exposed — did not.Fix
Add a
Free runner disk spacestep totest-ubuntu, gated on the same selective-laneskipoutput as the rest of the job's steps. It removes preinstalled toolchains this job never uses (dotnet, Android SDK, GHC, CodeQL, docker images), reclaiming ~25 GB — identical to the step already in the unit job.Verification
ci.ymlstill parses as valid YAML (python3 -c "import yaml; yaml.safe_load(...)").if:gating match the surrounding gated steps; skipped (selective-lane non-1) shards do not run it.