-
Notifications
You must be signed in to change notification settings - Fork 388
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
'Firefox' was not found in cypress/included:5.0.0
#363
Comments
FYI the package.json "test-cypress-ci": "start-server-and-test start 9966 'cypress run --browser $CYPRESS_BROWSER --headless'", |
Also seeing this on |
Same problem with |
@liunate since you run on GitHub Actions, why don't you use https://github.com/cypress-io/github-action ? Then 90% of the workflow yml file is probably unnecessary :) |
Could you try |
I solved the problem setting user as 1001 ( I'm using this image inside GitHub pipeline ) container:
image: cypress/browsers:node14.15.0-chrome86-ff82
options: --user 1001 --shm-size=2g |
Nice, but @paolocattani I would suggest simply running the Cypress tests using Firefox on GitHub Actions without Docker - because FF82 is pre-installed there. |
@bahmutov I just follow these instructions :D https://github.com/cypress-io/github-action#browser btw thanks for your advice, take a look to the pipeline if you want |
Thank you this is helpful 😃 |
Use container
cypress/included:5.0.0
at github actions shows firefox was not found or unsupported error in run log:p.s. Environment var
CYPRESS_BROWSER
is substituted in npm scripttest-cypress-ci
:"test-cypress-ci": "start-server-and-test start 9966 'cypress run --browser $CYPRESS_BROWSER --headless'"
Full log can be viewed at ci job log
The git workflow file is here
I also tried reverting to previous image such as 4.12.1 but it shows the same error
Strangely the very same image
cypress/included:5.0.0
works perfectly at local with command:docker run -it -v $PWD:/e2e -w /e2e -e CYPRESS_BROWSER=firefox --entrypoint=yarn cypress/included:5.0.0 test-cypress-ci
The text was updated successfully, but these errors were encountered: