cypress
cypress copied to clipboard
The Test Runner unexpectedly exited via a exit event with signal SIGSEGV
Current behavior
Some of our cypress tests failing with SIGSEGV when they are executed via test runner. Via UI mode the work just fine.
Desired behavior
The tests do not fail with SIGSEGV.
Test code to reproduce
https://github.com/schickermueller/Cypress_Clarity_SIGSEGV/tree/main
Cypress Version
13.6.3
Node version
v20.10.0
Operating System
linux-x64 (Ubuntu - 22.04), windows, mac
Debug Logs
(Run Starting)
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Cypress: 13.6.3 │
│ Browser: Electron 114 (headless) │
│ Node Version: v20.10.0 (/home/franz/.local/share/rtx/installs/node/20.10.0/bin/node)[3[0m │
│ 9m │
│ Specs: 1 found (sigv.cy.js) │
│ Searched: cypress/e2e/**/*.cy.{js,jsx,ts,tsx} │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
────────────────────────────────────────────────────────────────────────────────────────────────────
Running: sigv.cy.js (1 of 1)
The Test Runner unexpectedly exited via a exit event with signal SIGSEGV
Please search Cypress documentation for possible solutions:
https://on.cypress.io
Check if there is a GitHub issue describing this crash:
https://github.com/cypress-io/cypress/issues
Consider opening a new issue.
----------
Platform: linux-x64 (Ubuntu - 22.04)
Cypress Version: 13.6.3
Other
No response
I can indeed recreate this issue. This is a bug. This issue seems isolated to Electron.
I would suggest running your tests in another browser by passing --browser=chrome
to get around this issue for now.
I can also repro the issue with:
Platform: linux-x64 (Debian - 11.3) Node Version: v16.14.2 Cypress Version: 13.6.1 Chromium: 103
Switching --browser
from Chromium 103 to Chrome 103 "fixes" the Test Runner unexpectedly exited via a exit event with signal SIGSEGV
issue.
The issue can still be seen in version: v13.13.0
Investigation of this issue is now ongoing for half a year?
Any news on this issue? We are eperiencing the same in our devops yaml pipelines (with agents running on default Ununtu Latest - 2 cores, 8Gb RAM) We do prefer to run on Electron.
Experiencing the same issue. Thanks for the workaround @jennifer-shehane