-
Notifications
You must be signed in to change notification settings - Fork 40
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
Error: Unable to locate executable file: cachix. #138
Comments
I'm seeing the same thing. |
Workaround for cachix/cachix-action#138 Signed-off-by: Roman Volosatovs <rvolosatovs@riseup.net>
* fix: Continue on error for cachix step Quickfix for cachix/cachix-action#138 * oops * And for image building
Workaround for cachix/cachix-action#138 Signed-off-by: Roman Volosatovs <rvolosatovs@riseup.net>
Workaround for cachix/cachix-action#138 Signed-off-by: Roman Volosatovs <rvolosatovs@riseup.net>
We're seeing the same thing: https://github.com/runtimeverification/evm-semantics/actions/runs/4296996503/jobs/7489418708 I've tried version 14 and version 15 of the action. |
This is not an issue with this action. The latest nix release (2.14.0) has a regression which causes this. Pinning nix version in the nix-install-action resolves it:
|
Pin `nix` version to workaround an upstream regression: cachix/cachix-action#138 (comment) Signed-off-by: Roman Volosatovs <rvolosatovs@riseup.net>
Thank you! This solved my issue, closing |
We have to pin the GitHub actions nix version to v2.13.3 to avoid having the regression mentioned in cachix/cachix-action#138 (comment). This should fix the build CI. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
We have to pin the GitHub actions nix version to v2.13.3 to avoid having the regression mentioned in cachix/cachix-action#138 (comment). This should fix the build CI. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
We have to pin nix to v2.13.3 to avoid having the regression mentioned in cachix/cachix-action#138 (comment). This should fix the static builds. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Workaround for cachix/cachix-action#138 Signed-off-by: Roman Volosatovs <rvolosatovs@riseup.net>
Workaround for cachix/cachix-action#138 Signed-off-by: Roman Volosatovs <rvolosatovs@riseup.net>
Workaround for cachix/cachix-action#138 Signed-off-by: Roman Volosatovs <rvolosatovs@riseup.net>
Workaround for cachix/cachix-action#138 Signed-off-by: Roman Volosatovs <rvolosatovs@riseup.net>
We have to pin the GitHub actions nix version to v2.13.3 to avoid having the regression mentioned in cachix/cachix-action#138 (comment). This should fix the build CI. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
We have to pin nix to v2.13.3 to avoid having the regression mentioned in cachix/cachix-action#138 (comment). This should fix the static builds. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Workaround for cachix/cachix-action#138 Signed-off-by: Roman Volosatovs <rvolosatovs@riseup.net>
Workaround for cachix/cachix-action#138 Signed-off-by: Roman Volosatovs <rvolosatovs@riseup.net>
Workaround for cachix/cachix-action#138 Signed-off-by: Harald Hoyer <harald@hoyer.xyz>
Workaround for cachix/cachix-action#138 Signed-off-by: Harald Hoyer <harald@hoyer.xyz>
pin nix version to work-around regression cachix/cachix-action#138
Workaround for cachix/cachix-action#138 Signed-off-by: Roman Volosatovs <rvolosatovs@riseup.net>
In an attempt to fix cachix/cachix-action#138
In an attempt to fix cachix/cachix-action#138
In an attempt to fix cachix/cachix-action#138
In an attempt to fix cachix/cachix-action#138
I see the same thing on a self-hosted macos runner and I don't even know why. How does one debug this? |
This usually means that we can't find the cachix executable in your PATH. You can start tracking this down by echo-ing PATH during the workflow and making sure that it contains paths to the system/user nix profiles. |
I forgot to post an update. I fixed it couple of hours after posting. This was caused by GH action runner wiping the environment on start, discarding Nix environment. It's weird because it works fine on Linux, in similar setup. I think it's because shell is not being used to invoke commands on MacOS, while it is on Linux, or because DeterminateSystems installer is wiring things up differently between the two for some reason. The fix was to run |
A few minutes ago, all
cachix/cachix-action@v12
jobs started to fail with:E.g. https://github.com/rvolosatovs/wash/actions/runs/4295788214/jobs/7486677553
The text was updated successfully, but these errors were encountered: