question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The Test Runner unexpectedly exited via a exit event with signal SIGABRT on Chrome 92 headless and Cypress Version 8.3.0

See original GitHub issue

Current behavior

I am having troubles to run Cypress tests not only on my Jenkins machine but also on my laptop running them locally. It happened only sometimes but after upgrading to 8.3.0 I think it happens more often.

The execution gets stuck at some point as Cypress gives the SIGABRT signal.

I have seen https://github.com/cypress-io/cypress/issues/8865 issue, but it referrs to Electron, and it happens to me also in Chrome.

12:37:57   Running:  parental-control/contents-rating.spec.js                                      (35 of 65)
12:38:19 
12:38:19 
12:38:20   Parental Control - Contents - Full HD
12:48:20 Build timed out (after 10 minutes). Marking the build as aborted.
12:48:20 Xvfb stopping
12:48:20 Build was aborted
12:48:21 Archiving artifacts
12:48:22 Cypress error Error: The Test Runner unexpectedly exited via a exit event with signal SIGABRT
12:48:22 
12:48:22 Please search Cypress documentation for possible solutions:
12:48:22 
12:48:22 https://on.cypress.io
12:48:22 
12:48:22 Check if there is a GitHub issue describing this crash:
12:48:22 
12:48:22 https://github.com/cypress-io/cypress/issues
12:48:22 
12:48:22 Consider opening a new issue.
12:48:22 
12:48:22 ----------
12:48:22 
12:48:22 Platform: linux (Ubuntu - 18.04)
12:48:22 Cypress Version: 8.3.0

Desired behavior

Test runs properly until the end

Test code to reproduce

It happens on several tests

Cypress Version

8.3.0

Other

No response

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:7
  • Comments:11

github_iconTop GitHub Comments

3reactions
bukharovcommented, Aug 24, 2021

I get this when I close Cypress normally (via Cmd+Q or by clicking on the X).

Screen Shot 2021-08-24 at 6 14 23 PM

And then there’s this in the console:

Error: 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: darwin (20.5.0)
Cypress Version: 8.3.0
    at /Users/deniz/Work/cwealth-frontend-mono/node_modules/cypress/lib/errors.js:257:17
    at tryCatcher (/Users/deniz/Work/cwealth-frontend-mono/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/Users/deniz/Work/cwealth-frontend-mono/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/Users/deniz/Work/cwealth-frontend-mono/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/Users/deniz/Work/cwealth-frontend-mono/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/Users/deniz/Work/cwealth-frontend-mono/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/Users/deniz/Work/cwealth-frontend-mono/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/Users/deniz/Work/cwealth-frontend-mono/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/Users/deniz/Work/cwealth-frontend-mono/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/Users/deniz/Work/cwealth-frontend-mono/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (internal/timers.js:456:21) {
  known: true
}
2reactions
romankhomitskyicommented, Aug 30, 2021

The Same issue on cypress/included:8.3.1 Screenshot 2021-08-30 at 10 49 14

Read more comments on GitHub >

github_iconTop Results From Across the Web

The Test Runner unexpectedly exited via a exit event with ...
The Test Runner unexpectedly exited via a exit event with signal SIGABRT on Chrome 92 headless and Cypress Version 8.3.0 #17849.
Read more >
Cypress Test Runner unexpectedly exited via a exit event with ...
Current behavior: When I run my specs headless on the circleCI, Cypress closed unexpectedly with a socket error. Error message: The Test Runner...
Read more >
cypress-io/cypress - Gitter
node_modules/cypress/bin/cypress run --browser chrome The Test Runner unexpectedly exited via a exit event with signal SIGSEGV Please search Cypress ...
Read more >
Changelog - Cypress Documentation
In Cypress 12, we enforce running tests in a clean browser context through test isolation. This option is configurable, but is enabled by...
Read more >
cypress: Versions - Openbase
This fixes an issue where some command logs, like download or network events, are missing once Cypress has disconnected and then reconnected to...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found