Skip to content

ci: free runner disk before heavy builds (fix "No space left on device")#115

Merged
mighty840 merged 1 commit into
mainfrom
chore/ci-free-disk
Jun 23, 2026
Merged

ci: free runner disk before heavy builds (fix "No space left on device")#115
mighty840 merged 1 commit into
mainfrom
chore/ci-free-disk

Conversation

@mighty840

Copy link
Copy Markdown
Owner

Problem

CI on main started failing intermittently with:

rustc-LLVM ERROR: IO failure on output stream: No space left on device

in the Check, Lint, Test job (cargo test builds every integration-test artifact). ubuntu-latest ships only ~14 GB free, and orca's dep tree (wasmtime/bollard/hyper) + test artifacts tips over it. It's intermittent — the same code passed on the PR branch and at rc.5 — so it's runner disk pressure, not a code issue. (The rc.6 release binary still published fine; that build is just cargo build --release -p mallorca, no test artifacts.)

Fix

Add a Free disk space step to every ubuntu-latest job (check, build-arm64, e2e) and the release-binaries build: remove unused preinstalled SDKs (dotnet, android, ghc, CodeQL, boost) + prune docker images → reclaims ~20 GB. Prints df -h / for visibility.

No code changes; no version bump.

…device")

ubuntu-latest ships ~14GB free; orca's dep tree plus all the integration-test
artifacts intermittently exhausts it, failing `cargo test` with
"rustc-LLVM ERROR: IO failure on output stream: No space left on device".
Drop preinstalled SDKs we don't use (dotnet, android, ghc, CodeQL, boost) +
prune docker images to reclaim ~20GB, in every ubuntu-latest job (CI check /
arm64 / e2e) and the release-binaries build.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@mighty840 mighty840 merged commit e98ad58 into main Jun 23, 2026
3 checks passed
@mighty840 mighty840 deleted the chore/ci-free-disk branch June 23, 2026 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant