search

cypress-io / cypress

Fast, easy and reliable testing for anything that runs in a browser.
https://cypress.io
MIT License
46.43k stars 3.14k forks source link

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

Closed veronicamirada closed 1 year ago

veronicamirada commented 2 years ago

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

alexandrabusu commented 2 years ago

I have the same problem...

Failed to connect to Chrome, retrying in 1 second (attempt 36/62)
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.

it's happening when i'm trying to run the tests with cypress dashboard, this wasn't occurring before cypress 8.3.0

bukharov commented 2 years ago

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
}
bblwbtd commented 2 years ago

I also have this problem. Are there any temporary solutions?

peeyushohri04 commented 2 years ago

I am also facing the same issue , since upgrading to cypress 8.3.0 . Anyone Identified why the issue is being caused or any turn arounds to this issue ?

romankhomitskyi commented 2 years ago

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

skambo commented 2 years ago

Getting a similar error on 8.3.0 when running tests locally

Opening Cypress...
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 (19.6.0)
Cypress Version: 8.3.0
romankhomitskyi commented 2 years ago

I solved this issue by stop throwing DISPLAY and x11 socket. So that xvfb inside the docker understands that there is no need to send anything anywhere, and dealing with display virtualization on its own.

romankhomitskyi commented 2 years ago

You could try searching for XQuarts

tommy0831 commented 2 years ago

@romankhomitskyi Can you give more details? What do you mean by stop DISPLAY and x11 socket? What commands did you run?

romankhomitskyi commented 2 years ago

@romankhomitskyi Can you give more details? What do you mean by stop DISPLAY and x11 socket? What commands did you run?

I was getting this error when trying to run cypress in docker container with UI test runner, so I needed to pass x11 as a volume and display as variable to get it worked So I just removed them because I run cypress heedless now

tommy0831 commented 2 years ago

@romankhomitskyi Can you give more details? What do you mean by stop DISPLAY and x11 socket? What commands did you run?

I was getting this error when trying to run cypress in docker container with UI test runner, so I needed to pass x11 as a volume and display as variable to get it worked So I just removed them because I run cypress heedless now

Yes. I can confirm that running headless works. The problem is running with --headed option.

cypress-app-bot commented 1 year ago

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

cypress-app-bot commented 1 year ago

This issue has been closed due to inactivity.