10.3.0 regression - test runner randomly fails when running electron locally
See original GitHub issueCurrent behavior
So when running COMPONENT tests specs locally, the test runner randomly crashes out at varying specs. 🤔
ERR_FAILED (-2) loading 'http://localhost:51860/__/#/specs/runner?file=src/components/section-heading/section-heading.test.tsx'
Error: ERR_FAILED (-2) loading 'http://localhost:51860/__/#/specs/runner?file=src/components/section-heading/section-heading.test.tsx'
at rejectAndCleanup (node:electron/js2c/browser_init:161:7647)
at EventEmitter.stopLoadingListener (node:electron/js2c/browser_init:161:8022)
at EventEmitter.emit (node:events:390:28)
at EventEmitter.emit (node:domain:475:12)
Sometimes it fails at other specs. I have tested every single spec where it has crashed using cypress open - and all specs pass when run manually. I think there’s something up with the test runner inside of MACOS 12.4 (21F79)
Sometimes the test runner gets as far as (7 of 64) sometimes (16 of 64), and sometimes it gets to (26 of 64). 🤔 Im having a tough time trying to work out why the runner crashes out at various different specs, there is almost nothing else running while the cypress runner is working.
Desired behaviour
for all the specs to run, just like they do in CI
Test code to reproduce
Ill try and update this ticket with these details, but was hoping to gauge how many people are also finding this issue right now
Cypress Version
10.3.0
Other
Some other relevant dependencies:
"@emotion/css": "^11.5.0",
"react": "^17.0.2",
"react-dom": "^17.0.2"
"cypress-real-events": "^1.7.1",
"@cypress/code-coverage": "^3.10.0",
MacOS 12.4 (21F79)
running on an M1 MAX
Issue Analytics
- State:
- Created a year ago
- Reactions:5
- Comments:36 (18 by maintainers)
Top GitHub Comments
I should also note that I’m seeing this crash super reliably right after the 32nd spec, rather than jumping around to various locations as you described. Could possibly be an OS difference.
Alrighty! thats awesome intel, thank you @lmiller1990 - ill try and give that a go and see if the error still happens - and report back. 😃