Purge pip cache after build step in CI workflow #7031
Closed
+4
−0
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
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.
Motivation for features / changes
Our CI runs (including for our nightly releases) are failing.
Technical description of changes
The error reads
ERROR: Could not install packages due to an OSError: [Errno 28] No space left on device.It seems the provisioned virtual machine is running out of space. Our code hasn't had many changes, but it's possible that some of our dependencies have grown and/or the provisioned machine has less available space from the beginning, compared to before, for some reason (e.g. it comes with more things preinstalled).
Detailed steps to verify changes work correctly (as executed by you)
Due to security reasons, the CI workflow is read from submitted code/files, so we'll need to somehow merge this even if CI is not passing, and then see if this allows CI runs to pass.
EDIT: It seems this change was actually executed in the CI run for this PR. I'm not sure if I did something different in a previous attempt or where I got confused. Unfortunately, tho, this didn't seem to solve the problem.
Alternate designs / implementations considered (or N/A)
Alternatively, we'll need to figure out what we can delete from the provisioned machine, as suggested in https://github.com/orgs/community/discussions/25678