-
Notifications
You must be signed in to change notification settings - Fork 384
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
Transient CI HTTP 502 Bad Gateway errors #1168
Comments
Closing, as this issue appears not to be happening at the moment, although nothing I know about has changed to make it go away. |
Still occurring |
@MikeMcC399 Not sure why these were happening before, is this still occuring? |
It's a sporadic issue which keeps occurring. It could just be Cloudflare overload. |
I encountered the same issue (#1276). 4 attempts yet, most of circle CI tests have failed. It's either the tests which are failing (HTTP 504) or even the Docker build, during the npm download phase (npm error errno ECONNRESET). From one attempt to another, the tests are failing randomly, it's not always the same. |
The network seems to be working better today. I was able to get a successful CI run. |
Issue
The CI workflow circle.yml often experiences HTTP
502 Bad Gateway
errors causing CI to report an overall failure.Rerunning the workflow once or twice will usually recover. (Without write access to CircleCI it is not possible to re-run individual failed tests. I work around this by pushing a dummy amend commit which causes the whole workflow to be re-run.)
CI needs to be more reliable.
Background
cloudflare
Logs
https://app.circleci.com/pipelines/github/cypress-io/cypress-docker-images/2150/workflows/aca1a862-49bb-407b-90e9-4a3bb7b261a3/jobs/65630
https://app.circleci.com/pipelines/github/cypress-io/cypress-docker-images/2149/workflows/787f899c-1ca2-4c35-86bf-507b8a4731bb/jobs/65615
https://app.circleci.com/pipelines/github/cypress-io/cypress-docker-images/2134/workflows/9c75a08b-071b-4408-a634-08ef2bd258a6/jobs/65125
The text was updated successfully, but these errors were encountered: