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

🚀 - Update Cypress to 12.15.0 #530

Closed
nsbarsukov opened this issue Sep 25, 2023 · 0 comments · Fixed by #531
Closed

🚀 - Update Cypress to 12.15.0 #530

nsbarsukov opened this issue Sep 25, 2023 · 0 comments · Fixed by #531
Assignees
Labels
feature New feature or request P1 This issue has high priority

Comments

@nsbarsukov
Copy link
Member

Which package(s) are relevant/related to the feature request?

Don't known / other

Description

See error logs:

Still waiting to connect to Chrome, retrying in 1 second (attempt 58/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 59/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 60/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 61/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 62/62)
Cypress failed to make a connection to the Chrome DevTools Protocol after retrying for 50 seconds.

This usually indicates there was a problem opening the Chrome browser.

The CDP port requested was 34071.

Error: connect ECONNREFUSED 127.0.0.1:34071
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:11[87](https://github.com/taiga-family/maskito/actions/runs/6286561265/job/17070207105?pr=527#step:6:88):16)

Error: Process completed with exit code 1.

Why?

@nsbarsukov nsbarsukov added feature New feature or request P1 This issue has high priority labels Sep 25, 2023
@nsbarsukov nsbarsukov self-assigned this Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request P1 This issue has high priority
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant