Skip to content

Allow disabling the pip cache task #658

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

EraYaN
Copy link

@EraYaN EraYaN commented May 7, 2025

This helps a lot when you have reused and persistent self-hosted runners. The pip cache dir gets to be enourmous after a while slowing down this task.

@EnricoMi
Copy link
Owner

Maybe we can improve the caching and fix the growth of the cache. Do you know why it grows? Do you have a public repo that exhibits this behaviour?

@EraYaN
Copy link
Author

EraYaN commented May 22, 2025

I do not have a public repo sadly, it's a specific infrastructure problem. This is because it uses persistent self-hosted runners (so other pipeline steps use the same cache). This results in the cache task uploading the organisation wide cache, even though it is already persistent, so it just wastes time. It really needs to be disabled, improving it means not running it.

@EnricoMi
Copy link
Owner

So I presume your pipelines install other PIP packages, which all end up in the cache of this action.

This action should use an isolated cache, then there should be no such side effects. I'll look into this.

@EraYaN
Copy link
Author

EraYaN commented May 22, 2025

In general it is okay to just not use a cache at all, it will still be faster than using the cache.

EnricoMi added a commit that referenced this pull request May 25, 2025
@EnricoMi
Copy link
Owner

Fix #668 should improve your use case while continuing to work as it used to for other users.

@EnricoMi EnricoMi closed this May 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants