Remove pip cache in GitHub Actions#2776
Merged
zcbenz merged 2 commits intoml-explore:mainfrom Nov 16, 2025
Merged
Conversation
zcbenz
force-pushed
the
ci-pip-cache
branch
4 times, most recently
from
585745a to
deefeb9
Compare
zcbenz
changed the title
zcbenz
changed the title
zcbenz
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
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.
I made some test runs to see how much time pip cache can save.
For normal linux build it saved 10s in build time (when most pip installs happen) but it is probably just noise.
For CUDA build, the build time reduced 40s but the setup time (when cache is uncompressed) increased 1m50s, it is likely because the cache size is too large (4GB). I also saw similar reports in actions/setup-python#330.
So I think we should just remove the pip cache.