2nd attempt at disk usage reduction for IceTray Runner #863
Conversation
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
RasmusOrsoe
changed the title
Aske-Rosted
approved these changes
Jan 10, 2026
Collaborator
Aske-Rosted
left a comment
Aske-Rosted
left a comment
There was a problem hiding this comment.
seems pretty non-controversial to me. Hopefully we do not have to think about runner disk space for a while now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
While #861 appeared to be solved in #860, updates to #857 showed that new variations in the workflow disk usage made the runner fail again.
These variations are largely out of our control; caused by infrastructure changes in GitHub and dependency changes.
In this PR, an additional step is added in the IceTray runner installation procedure, that avoid downloading cuda-versions of torch. This reduces the dependency-induced variation in disk usage, and the disk requirements by the installation from 6gb - 2gb.
This should create enough headroom for the workflow to be robust against future variations.