-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
The Test Runner unexpectedly exited via a exit event with signal SIGSEGV (Error: This socket has been ended by the other party) #6478
Comments
Duplicate of #6458 |
@jennifer-shehane I don't think this is a duplicate issue. It looks like the stack traces are different. #6458 has a path to the Cypress app in the stack trace and this one doesn't.
We're running into this too, with the stack trace mentioned in this issue:
on node Any idea what might be causing this? |
More info on this, I was running the test with I'm seeing the crash happen mid
The log ending is exactly as reported, i.e. before the JS string ends, it logs that the CLI receives an exit signal. |
Current behavior:
Cypress is crashing on each run even in all browsers listed inside the options to run.
I can't figure out what it can be, so I hope for your help guys.
Thanks first of all for such a great tool for testing!
Stacktrace:
The Test Runner unexpectedly exited via a exit event with signal SIGSEGV
Desired behavior:
Should work without crashing at least.
Test code to reproduce
Versions
Platform: darwin (19.3.0)
Cypress Version: 4.0.2
The text was updated successfully, but these errors were encountered: