ci: drop no-op /mnt build-storage staging from setup-build-env#6
Open
MattDHill wants to merge 1 commit into
Open
ci: drop no-op /mnt build-storage staging from setup-build-env#6MattDHill wants to merge 1 commit into
MattDHill wants to merge 1 commit into
Conversation
GitHub's ubuntu-24.04 runners have a single ~145 GB root disk with no separate /mnt (verified across runner images, May–June), so the June 25 "stage build storage on /mnt" change relocated Docker's data-root and start-cli's pack scratch within the same filesystem and freed nothing. It was a no-op that nonetheless created the false confidence behind dropping FREE_DISK_SPACE from GPU packages (which broke llama-cpp's rocm release). Remove the staging step and the docker runtime-basedir override. Disk headroom for large/GPU builds is unchanged: it stays on the per-package FREE_DISK_SPACE knob (reactive, off by default, gated free-disk-space step) — restored on the packages that need it separately. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
MattDHill
force-pushed
the
ci/fix-gpu-build-disk-headroom
branch
from
da1f6fe to
b5eb17e
Compare
MattDHill
changed the title
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.
GitHub's
ubuntu-24.04runners have a single ~145 GB root disk with no separate/mnt(verified across runner images spanning May–June). The June 25 "stage build storage on/mnt" change therefore relocated Docker's data-root and start-cli's pack scratch within the same filesystem and freed nothing — a no-op that nonetheless created the false confidence behind droppingFREE_DISK_SPACEfrom GPU packages (which is what broke llama-cpp's rocm release).This removes the dead staging:
setup-build-env: drop the/mntstaging step and the dockerruntime-basediroverride.No workflow-gating or input changes — disk headroom for large/GPU builds stays on the per-package
FREE_DISK_SPACEknob (reactive, off by default, gatedfree-disk-spacestep), restored on the packages that actually need it (e.g. llama-cpp) separately. No package files change here.🤖 Generated with Claude Code