Conversation
Collaborator
✅ Heimdall Review Status
|
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
|
No issues found. This is a well-scoped CI fix. The two changes are straightforward and correct:
|
danyalprout
approved these changes
Apr 4, 2026
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
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.
Summary
Two separate failure modes were causing no-space-left crashes on CI runners. First, the jlumbroso/free-disk-space action uses apt-get internally and silently fails when the disk is already critically full, leaving nothing freed before cache restoration or compilation. This is fixed by adding a fast rm -rf pre-clean step that removes Android SDK, .NET, GHC, Boost, and CodeQL (~15-20 GB) before apt-based cleanup runs. Second, the test-musl-sigsegv job was restoring the shared stable Rust cache, a multi-GB artifact set it has no use for given it only builds one package for a specific target. Removing that cache key eliminates the root cause of its failures.