ci(qemu): rm_work + aggressive disk reclaim to fit GHA's 30 GB#8
Merged
Conversation
First end-to-end qemu-runtime dispatch ran 4.5 hours then died at vscode's do_unpack with tar exit 2. The build itself was working; the 200 MB VSCode tarball + its uncompressed expansion was the straw that broke the 30 GB disk camel. Two fixes: - INHERIT += rm_work so every recipe's workdir gets scrubbed right after do_package, reclaiming 5-15 GB over the build. - More aggressive Free-disk-space step: also nuke /usr/local/.ghcup + the rest of /opt/hostedtoolcache/* + docker's preloaded images. Adds ~10-15 GB headroom upfront.
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.
First qemu-runtime dispatch ran 4.5 hours then died at vscode's do_unpack with tar exit 2 — almost certainly out-of-disk on the GHA hosted runner (full Weston image sstate + workdir + the 200 MB VSCode tarball expansion blew past the 30 GB cap).
Two fixes: