feat(env-setup): add free_disk_space toggle for disk-constrained runners#26
Merged
AndriiTsok merged 1 commit intomainfrom Apr 18, 2026
Merged
feat(env-setup): add free_disk_space toggle for disk-constrained runners#26AndriiTsok merged 1 commit intomainfrom
AndriiTsok merged 1 commit intomainfrom
Conversation
GitHub-hosted ubuntu runners start with ~14 GB free but ship pre-loaded with Android SDK, .NET, Haskell, and several GB of Docker images that a typical Rust/Nx build never touches. On the mcpg workspace the cold full-rebuild hit disk-full during the build step (tests + llvm-cov instrumentation + sccache staging + 28-crate target/debug + wasm target exceeded the ceiling) even after dropping redundant build targets. Opt-in via `free_disk_space: true` in `.environment.yml`. When set, runs jlumbroso/free-disk-space@v1.3.1 right after the parser — before any install/compile step — with a conservative profile: android: true ~11 GB dotnet: true ~2 GB haskell: true ~5 GB docker-images: true ~3 GB tool-cache: false keep Node/Python/Go pre-installs swap-storage: false keep swap (Rust linker still benefits) large-packages: false slow, marginal gain Expected: ~18–20 GB free after the step vs ~14 GB baseline — more than enough headroom for the mcpg workload. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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
mcpg-dev/source-code PR #22 hit "No space left on device" during the build step after tests completed. Cold full-rebuild of 28 crates + llvm-cov instrumentation + sccache local cache + wasm32-wasip2 target tree + redis/nats binaries exceeds the ~14 GB runner ceiling.
Fix
New
.environment.ymlfield:When set (Linux only), runs
jlumbroso/free-disk-space@v1.3.1right after the config parser — before any install/compile step — with a conservative profile:Expected ~18–20 GB free after the step vs ~14 GB baseline.
Opt-in — default
false— so existing consumers don't pay the ~30–60s cleanup cost they don't need.🤖 Generated with Claude Code