Skip to content
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

Cache restore fails on self-hosted windows runners #51

Open
melund opened this issue Dec 5, 2023 · 2 comments
Open

Cache restore fails on self-hosted windows runners #51

melund opened this issue Dec 5, 2023 · 2 comments

Comments

@melund
Copy link

melund commented Dec 5, 2023

I stumbled on this problem with out self-hosted windows runners.

It doesn't cause the action to fail, so I only saw by chance.

image

It looks like the cache is downloading but tar fails when trying to extract it, reporting that the file is missing. I tried to look in the temp folder while the pipeline is running, and there is no cache.tgz file in the folder.

@pavelzw
Copy link
Collaborator

pavelzw commented Dec 6, 2023

It seems like there is no gzip installed on your self-hosted windows runner. What happens when you install it?

I don't think that this issue is setup-pixi specific.
It will probably also occur if you use actions/cache@v3 directly; both setup-pixi and actions/cache use the Nodejs library @actions/cache internally.

@pavelzw pavelzw closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2023
@melund
Copy link
Author

melund commented Dec 6, 2023

It seems like there is no gzip installed on your self-hosted windows runner. What happens when you install it?

Fair enough. It is true that gzip (MSYS2) wasn't installed. But neither is tar, and setup-pixi falls back to the version in "Git for Windows". GZip is in the same folder as the tar version it is using.
I agree that it is not nice to use tar and gzip bundled with Git. But pixi is already using one fallback.

It will probably also occur if you use actions/cache@v3

No. That seems to works fine :) May it works a bit differently

@pavelzw pavelzw reopened this Dec 6, 2023
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

No branches or pull requests

2 participants