You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
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
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.
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 nocache.tgz
file in the folder.The text was updated successfully, but these errors were encountered: