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.

Unexpectedly exiting with signal SIGSEGV since 8.6.0 version

See original GitHub issue

Current behavior

Since cypress 8.6.0 upgrade, I’m experiencing aleatory errors in my pipelines, sometimes works fine until the end, and sometimes not. The error is the next:

The Test Runner unexpectedly exited via a exit event with signal SIGSEGV

I also started to see this error at the logs, but seems to work ok sometimes, so I’m no prety sure is the route cause of this:

[6606:1028/125808.622484:ERROR:bus.cc(392)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")

The only pissible solution for those issues is downgrading to cypress 8.5.0, and in this version everything works fine for me.

Desired behavior

I don’t know how I can upgrade cypress and maintain the 8.5.0 behaviour.

Test code to reproduce

cypress.json: { “viewportWidth”: 1920, “viewportHeight”: 1080, “video”: false, “reporter”: “junit”, “reporterOptions”: { “mochaFile”: “cypress/results/test-results.[hash].xml”, “toConsole”: true }, “pageLoadTimeout”: 120000, “retries”: { “runMode”: 2, “openMode”: 2 }, }

package.json@cypress/skip-test”: “^2.6.1”, “cypress”: “8.7.0”, “cypress-file-upload”: “^5.0.8”, “cypress-grep”: “^2.5.1”, “cypress-wait-until”: “^1.7.1”,

Cypress Version

8.6.0 and 8.7.0

Other

No response

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:32
  • Comments:15 (2 by maintainers)

github_iconTop GitHub Comments

4reactions
marlonmarcellocommented, Dec 13, 2021

Can confirm, same issue on v9.1.1

2reactions
edenhermelincommented, Nov 24, 2021

happens also on the latest version…

Read more comments on GitHub >

github_iconTop Results From Across the Web

Cypress Test Runner unexpectedly exited via a exit event with ...
Issue resolved by reverting back cypress version to 7.6.0. ... the operating system sends your process a signal (SIGSEGV on Mac & Linux, ......
Read more >
How to solve the 'Signal: SIGSEGV (Segmentation fault)' error ...
Segmentation fault means that you get a runtime error. Runtime error may be caused by : Using a number that does not have...
Read more >
SIGSEGV: Linux Segmentation Fault | Signal 11, Exit code 139
In Unix/Linux, SIGSEGV is operating system signal 11; In Docker containers, when a Docker container terminates due to a SIGSEV error, it throws...
Read more >
8.6 Release Notes Red Hat Enterprise Linux 8
This update provides new enhancements and bug fixes, most notably: The pcscd daemon no longer automatically exits after inactivity when started manually. The ......
Read more >
Bug listing with status RESOLVED with resolution OBSOLETE ...
... crashes with signal 10 (bus error)" status:RESOLVED resolution:OBSOLETE ... "sys-apps/portage-2.2: fails to build with "exited unexpectedly" message ...
Read more >

github_iconTop Related Medium Post

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