-
Notifications
You must be signed in to change notification settings - Fork 10
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
Pixi location change breaks self-hosted runner #66
Comments
NOTE: rebasing the other branch didn't help this. Do I need to manually intervene on the self-hosted runner? |
Maybe you could change the cache key so that the cache is busted? |
My action for setting this up looks like this: - name: Setup pixi
uses: prefix-dev/[email protected]
with:
pixi-version: v0.12.0
# Don't use $HOME/.pixi to work around self-runner env issues
# https://github.com/prefix-dev/setup-pixi/issues/25
pixi-bin-path: ${{ runner.temp }}/bin/pixi
post-cleanup: true
cache: true I'm not sure how I'd change the cache key. Should I disable cache for now? |
I've disabled cache for now, and my CI is passing again. It would be good to understand the proper upgrade path in future, since I've hit a bug like this twice. Perhaps I'm doing something wrong. |
The cache key should incorporate the pixi environment path... strange |
Can you try rerunning it with debug logging enabled? If I remember correctly it then tells you how the cache key is constructed https://github.com/prefix-dev/setup-pixi/blob/main/.github/assets/enable-debug-logging-dark.png?raw=true |
#67 now also incorporates the pixi version in the cache. Not sure what exactly the problem in your case is (the sha should already have incorporated the change from |
Thanks for the fast turn around on this. I tried using
I notice warnings from other jobs:
I enabled debug info:
|
Thanks! Found the error: |
I think the easiest way to fix this is to add the CWD to the cache key as well. |
Fixed in |
Confirming that |
Today I updated our
main
branch to use pixi v0.12.0 and setup-pixi to v0.4.1. After this, I continued work on another branch, which was behindmain
, and my CI jobs fail as follows:We are using a self-hosted runner for our CI/CD jobs. I had a similar issue in the past with cache on self-hosted runners when upgrading (#25), but this seems slightly different.
The text was updated successfully, but these errors were encountered: