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

Error finding chrome on subsequent runs (macOS self-hosted runner) #604

Open
twyatt opened this issue Sep 18, 2024 · 2 comments · May be fixed by #612
Open

Error finding chrome on subsequent runs (macOS self-hosted runner) #604

twyatt opened this issue Sep 18, 2024 · 2 comments · May be fixed by #612

Comments

@twyatt
Copy link

twyatt commented Sep 18, 2024

First run:

Run browser-actions/setup-chrome@v1
Setup chrome latest
Attempting to download chrome latest...
Acquiring chrome 1357145 from https://www.googleapis.com/download/storage/v1/b/chromium-browser-snapshots/o/Mac_Arm%2F1357145%2Fchrome-mac.zip?alt=media
Installing chrome...
/usr/bin/unzip -o -q /Users/ci/actions-runner/_work/_temp/f3df1bf0-cf5b-420c-b4ef-6c190d48a4f7
Successfully Installed chromium to /Users/ci/actions-runner/_work/_tool/setup-chrome/chromium/1357145/arm64
/Users/ci/actions-runner/_work/_tool/setup-chrome/chromium/1357145/arm64/Chromium.app/Contents/MacOS/Chromium --version
Chromium 131.0.6726.0 
Successfully setup chromium 131.0.6726.0

Subsequent runs:

Run browser-actions/setup-chrome@v1
Setup chrome latest
Found in cache of chrome latest @ /Users/ci/actions-runner/_work/_tool/setup-chrome/chromium/1357145/arm64
Error: Unable to locate executable file: /Users/ci/actions-runner/_work/_tool/setup-chrome/chromium/1357145/arm64/chrome. 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.

Inspecting the downloaded ZIP file, the chrome executable does in fact not exist.

@davertay davertay linked a pull request Oct 3, 2024 that will close this issue
@davertay
Copy link

davertay commented Oct 3, 2024

@twyatt I didn't test it yet, but I started on a fix in #612

As a workaround, I think if you set the chromium version to stable it will use the channel specific installer which looks like it has the correct path.

@davertay
Copy link

davertay commented Oct 3, 2024

According to the docs, this is the syntax:

steps:
  - uses: browser-actions/setup-chrome@v1
    with:
      chrome-version: stable

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

Successfully merging a pull request may close this issue.

2 participants