-
Notifications
You must be signed in to change notification settings - Fork 374
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
[github actions] unable to solve process (bash) when downloading building cypress/factory #1005
Comments
@jennifer-shehane I see this was removed from Cypress App Triage, will anyone still answer the question I made? Perhaps I am not using |
Could be totally unrelated, but I got the same error. Maybe it's caused by Google rotating their signing keys: |
@FranciscoKloganB Is this still an issue? |
Hi, I am also facing the same issue, not seeing anything special in my docker file. weirdly only an issue inside a GitHub action
|
Node.js 16 entered end-of-life on Sep 11, 2023. Are you still seeing this issue with a supported version of Node.js and using |
I have recently created a GitHub Action that periodically executes a set of smoke tests every 30m using Cypress. Since execution is frequent and the intention is to have fast feedback. We have created a custom workflow and a custom docker image based on
cypress/factory
image, instead of using cypress official action. We have effectively reduced the execution time of E2E tests (battery) from 12m down to 7m and the smoke test execution time from 8m to 3m.These smoke tests run 48 times a day. We are no where near reaching the limit of our GitHub quotas, or bandwidth limits. Yet, the smoke tests fail on average 4% of the times that they run. With the following error:
This does not appear to be a problem on our side (see workflow and dockerfile below). It appears to be related with the
cypress/factory
dockerfile itself.If not... Are there any pointers you can provide to us in order to fix this issue?
Below you can find our Dockerfile and the relevant parts of our GitHub Workflow
The text was updated successfully, but these errors were encountered: