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

Version 2.1.8 breaks self-hosted macOS ARM Github Actions runner #735

Open
cknitt opened this issue Dec 7, 2023 · 5 comments
Open

Version 2.1.8 breaks self-hosted macOS ARM Github Actions runner #735

cknitt opened this issue Dec 7, 2023 · 5 comments

Comments

@cknitt
Copy link

cknitt commented Dec 7, 2023

We have a self-hosted macOS ARM Github Actions runner for the ReScript CI.

Since setup-ocaml 2.1.8, we are getting the following error in CI on that runner (see e.g. https://github.com/rescript-lang/rescript-compiler/actions/runs/7117236442/job/19378552445):

Run ocaml/setup-ocaml@v2
Retrieve the opam cache
Install opam
Initialise the opam state
Error: Unable to locate executable file: brew. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.

This is probably due to this change? 2d84a0f

@smorimoto
Copy link
Member

Yeah, that's definitely the cause.
Actually, this action doesn't officially support self-hosted runners yet.
I think the short term workaround is to expose the environment variable.

@cknitt
Copy link
Author

cknitt commented Dec 8, 2023

I think the short term workaround is to expose the environment variable.

What exactly do you mean? Expose the environment variable where/how?

@smorimoto
Copy link
Member

smorimoto commented Dec 9, 2023

Just set GITHUB_ACTIONS to true on the runner.

@cknitt
Copy link
Author

cknitt commented Dec 12, 2023

I tried:

  1. Starting the self-hosted runner with GITHUB_ACTIONS=true ./run.sh. This did not have any effect.
  2. Setting the variable in the Github actions admin UI. This is not allowed, see screenshot.

Am I missing something?

Bildschirmfoto 2023-12-12 um 15 09 09

@smorimoto
Copy link
Member

It's pretty weird that 1 doesn't work. How about explicitly exporting the environment variable globally?

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