-
Notifications
You must be signed in to change notification settings - Fork 41
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
Bump from 2.3.3 to 3.10 - RangeError: Maximum call stack size exceeded #325
Comments
I did the migration steps from v2 to v3 according to the documentation |
Yikes, looks like this is impacting headless runs too. This is related to a Cypress bug: cypress-io/cypress#15101 The reason 2.x doesn't have this issue is because we use a node task to execute the health check (which has always been a workaround). In 3.x we were able to remove that hack, but now we're being bit by this networking bug in Cypress. You can replace Related to #315 & #320. Going to leave this open until the bug is fixed in Cypress upstream. |
thanks for clarifying @Robdel12 |
@Robdel12 I created a reproducible repo https://github.com/iondrimba/cypress_maximum_call_stack |
@Robdel12 Updated the reproducible repo with a successful case without percy |
Almost ready cypress-io/cypress#16311 🎉 |
Very exciting!! 👀 |
Going to guess everything is smooth on 7.3.0+ now? If so I'll close this out 😃 |
Everything works now on the latest cypress release 7.3.0 |
After upgrading a personal project to version 3.1.0 some of my cypress spec started failing with the error below
I'm using cypress 7.1.0
Rolling back to version 2.3.4 everything works ok
The text was updated successfully, but these errors were encountered: