The Test Runner unexpectedly exited via a exit event with signal SIGABRT - Assertion `(env) != nullptr' failed #8865

daftspaniel · 2020-10-16T13:24:54Z

Current behavior

Test suites sometimes crashing after successful run.

    ✔  All specs passed!                        16:16      356      356        -        -        -  

/root/.cache/Cypress/5.4.0/Cypress/Cypress[242]: ../../third_party/electron_node/src/api/callback.cc:226:MaybeLocal<v8::Value> node::MakeCallback(v8::Isolate *, Local<v8::Object>, Local<v8::Function>, int, Local<v8::Value> *, node::async_context): Assertion `(env) != nullptr' failed.
The Test Runner unexpectedly exited via a exit event with signal SIGABRT

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.

Desired behavior

Good exit code

Test code to reproduce

With assistance I can perhaps narrow this down from 356 tests. Some suites work fine but two continually fail.

Versions

Cypress 5.40
Linux running on CircleCI

The text was updated successfully, but these errors were encountered:

jonataswalker · 2020-10-19T12:36:01Z

Same issue on Azure Pipeline.

andreasremdt · 2020-10-21T09:00:13Z

I can confirm the same thing happening on Jenkins (Ubuntu 18.04). If desired, I can provide additional debug logs or information.

jennifer-shehane · 2020-10-21T11:06:19Z

Yes, DEBUG logs may be helpful. Perhaps this is due to Electron upgrade in 5.4.0. #8406

andreasremdt · 2020-10-21T13:49:59Z

I just uploaded the last part of the debug log, since it's huge.
Seems to be an issue with Electron indeed. Let me know if you need the entire log, I would look for an option to limit the test cases then.

cypress.log

TomaszG · 2020-10-27T11:28:09Z

Any update on this? Is there some more information needed? I'm facing the issue as well after upgrading to 5.5.0.

kamiloski · 2020-10-30T09:50:38Z

Bug still exists in 5.5.0

daftspaniel · 2020-11-03T14:55:35Z

@jennifer-shehane Do you need additional logs on this or the ones Andrea provided sufficient? Many thanks.

diggabyte · 2020-11-03T23:10:43Z

Also seeing in 5.5.0 (electron)

laurentpierson · 2020-11-04T11:47:28Z

I'm also getting the same issue with Cypress 5.5.0 when running Electron headless.

mathew-ferry13 · 2020-11-06T19:08:56Z

Same issue here - Started with 5.4.0 and not fixed in 5.5.0. Everything was working fine with 5.3.0

tamaserdfalvi · 2020-11-09T16:14:28Z

Also seeing this both when building with Jenkins (Ubuntu) and locally on OSX Catalina

tkharuk · 2020-11-10T10:44:36Z

Initially, I thought it happens due to retries and some flaky tests since some of my tests do fail at least once.

hannalapitanware · 2020-11-10T14:57:19Z

@jennifer-shehane is it possible to provide approximate Cypress version with fixes? Thank you in advance!

tamaserdfalvi · 2020-11-10T16:38:44Z

Just saw Cypress 5.6.0 coming out, but if it isn't fixed in that, we have to stick to 5.3.0 unfortunately as otherwise all our test runs will fail in Jenkins, making it absolutely unusable :(

jonataswalker · 2020-11-10T20:12:31Z

Sad because cy.route2() is just a great new feature.

It's true that it is a 5.3.0 feature but there were a lot of fixes after that.

mathew-ferry13 · 2020-11-12T14:36:39Z

Just upgraded to Cypress 5.6.0 and experienced the same issue

TomaszG · 2020-11-13T10:05:02Z

Is there any workaround for it? I would like to update Cypress to the latest version, however, this issue blocks me as it breaks the whole CI process. Are there any plans of fixing it in the near future? If not then I may think of supressing the exit code returned by the Cypress using e.g. custom docker entry point or something similar.

Manuel-Suarez-Abascal · 2020-11-13T16:25:10Z

I have encountered the same issue after upgrading to the latest Cypress version from 5.1.*. I wonder if there is any resolution for it?

Cypress version: 5.6.0
OS: Ubuntu 18.04.5 LTS

jennifer-shehane · 2020-11-17T05:49:25Z

There is a situation where Cypress will occasionally exit with SIGABRT, SIGTERM, or SIGSEGV and a non-zero exit code when experimentalSourceRewriting is set to true. Please follow this issue for updates if your SIG error disappears when setting experimentalSourceRewriting: false. #9208

This may not be the issue for everyone in this thread however, so we will leave this issue open to track the cause of any other SIGABRT errors.

andreasremdt · 2020-11-17T08:28:53Z

In our example, we don't (and never have) use experimentalSourceRewriting, but still, since the release of Cypress 5.4.0, every single test run on our CI (Jenkins) fails. Can I provide you with any more information, such as logs?

vincentaudoire · 2020-11-17T08:45:25Z

We're facing the same issue on GitHub Action. Here's some of the logs:

/home/runner/.cache/Cypress/5.6.0/Cypress/Cypress[5808]: ../../third_party/electron_node/src/api/callback.cc:226:MaybeLocal<v8::Value> node::MakeCallback(v8::Isolate *, Local<v8::Object>, Local<v8::Function>, int, Local<v8::Value> *, node::async_context): Assertion `(env) != nullptr' failed.
200
Error: The Test Runner unexpectedly exited via a exit event with signal SIGABRT
201

202
Please search Cypress documentation for possible solutions:
203

204
https://on.cypress.io
205

206
Check if there is a GitHub issue describing this crash:
207

208
https://github.com/cypress-io/cypress/issues
209

210
Consider opening a new issue.
211

212
----------
213

214
Platform: linux (Ubuntu - 16.04)
215
Cypress Version: 5.6.0
216
    at /home/runner/work/private-signup/private-signup/node_modules/cypress/lib/errors.js:279:17
217
    at tryCatcher (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/util.js:16:23)
218
    at Promise._settlePromiseFromHandler (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/promise.js:547:31)
219
    at Promise._settlePromise (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/promise.js:604:18)
220
    at Promise._settlePromise0 (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/promise.js:649:10)
221
    at Promise._settlePromises (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/promise.js:729:18)
222
    at Promise._fulfill (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/promise.js:673:18)
223
    at Promise._resolveCallback (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/promise.js:466:57)
224
    at Promise._settlePromiseFromHandler (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/promise.js:559:17)
225
    at Promise._settlePromise (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/promise.js:604:18)
226
    at Promise._settlePromise0 (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/promise.js:649:10)
227
    at Promise._settlePromises (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/promise.js:729:18)
228
    at Promise._fulfill (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/promise.js:673:18)
229
    at Promise._resolveCallback (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/promise.js:466:57)
230
    at Promise._settlePromiseFromHandler (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/promise.js:559:17)
231
    at Promise._settlePromise (/home/runner/work/private-signup/private-signup/node_modules/bluebird/js/release/promise.js:604:18) {
232
  known: true
233
}
234
Error: The Test Runner unexpectedly exited via a exit event with signal SIGABRT

kamiloski · 2020-11-19T12:53:11Z

There is a situation where Cypress will occasionally exit with SIGABRT, SIGTERM, or SIGSEGV and a non-zero exit code when experimentalSourceRewriting is set to true. Please follow this issue for updates if your SIG error disappears when setting experimentalSourceRewriting: false. #9208

This may not be the issue for everyone in this thread however, so we will leave this issue open to track the cause of any other SIGABRT errors.

Doesn't work for me v 5.6.0

jonataswalker · 2020-11-24T11:42:35Z

At least on Azure Pipeline v6.0.0 solved this issue.

I guess it was the electron upgrade.

tamaserdfalvi · 2021-01-25T15:01:12Z

Upgrading to 6.3.0 no longer throws this error on our Ubuntu/jenkins so looks like I can finally move on from 5.3.0

FromStoneage · 2021-01-26T00:45:47Z

I can concur 6.3.0 solves the issue, works fine on the azure pipeline now.

pedroAVS · 2021-01-29T10:59:21Z

It's also occuring in version 6.3.0
running in chrome browser and not uploading/downloading any file
Running multiple parallel spec files on Jenkins in a Pod with 4000m cpu and 8Gi of memory

jennifer-shehane · 2021-03-24T18:54:42Z

Are people still experiencing this in the current version of Cypress? I see some indication that some people's issues were fixed and no one has commented since January. Would love some feedback.

grantral · 2021-03-25T07:30:06Z

Are people still experiencing this in the current version of Cypress?

Yes.

I'm seeing this issue on GitLab 13.9.3 with GitLab Runner 13.9.0 with Cypress 6.8.0 with cypress/base:14.6.0.

.gitlab-ci.yml

cypress:
image: cypress/base:14.16.0
stage: test
before_script:
  - export DEBUG=cypress:*
  - npm ci
  - npm run cy:info
  - npm run cy:verify
  - npm run cy:version
script:
  - npm run cy:run

log

$ npm run cy:info
> e2e-tests@1.0.0 cy:info /builds/grantral/e2e-tests
> cypress info
2021-03-25T07:12:14.388Z cypress:cli:cli cli starts with arguments ["/usr/local/bin/node","/builds/grantral/e2e-tests/node_modules/.bin/cypress","info"]
2021-03-25T07:12:14.389Z cypress:cli NODE_OPTIONS is not set
2021-03-25T07:12:14.389Z cypress:cli:cli program parsing arguments
2021-03-25T07:12:14.493Z cypress:cli undefined DISPLAY environment variable
2021-03-25T07:12:14.493Z cypress:cli Cypress will spawn its own Xvfb
2021-03-25T07:12:14.494Z cypress:cli needs to start own Xvfb? true
2021-03-25T07:12:14.495Z cypress:cli Starting Xvfb
2021-03-25T07:12:14.533Z cypress:cli spawning, should retry on display problem? false
2021-03-25T07:12:14.537Z cypress:cli passing DISPLAY :99
2021-03-25T07:12:14.537Z cypress:cli spawning Cypress with executable: /root/.cache/Cypress/6.8.0/Cypress/Cypress
2021-03-25T07:12:14.538Z cypress:cli spawn args [ '--no-sandbox', '--', '--mode=info', '--cwd', '/builds/grantral/e2e-tests' ] { detached: false, stdio: [ 'inherit', 'inherit', 'pipe' ] }
2021-03-25T07:12:14.546Z cypress:cli piping child STDERR to process STDERR
cypress:ts Running without ts-node hook in environment "production" +0ms
cypress:server:appdata path: /root/.config/Cypress/cy/production/browsers +0ms
cypress:server:util:node_options NODE_OPTIONS check passed, not forking { NODE_OPTIONS: '--max-http-header-size=1048576' } +0ms
cypress:server:util:node_options restoring NODE_OPTIONS { NODE_OPTIONS: '--max-http-header-size=1048576', ORIGINAL_NODE_OPTIONS: undefined } +1ms
cypress:server:cypress starting cypress with argv [ '/root/.cache/Cypress/6.8.0/Cypress/Cypress', '--no-sandbox', '--', '--mode=info', '--cwd', '/builds/grantral/e2e-tests' ] +0ms
cypress:server:args argv array: [ '/root/.cache/Cypress/6.8.0/Cypress/Cypress', '--no-sandbox', '--mode=info', '--cwd', '/builds/grantral/e2e-tests' ] +0ms
cypress:server:args parsed argv options { options: { _: [ '/root/.cache/Cypress/6.8.0/Cypress/Cypress' ], sandbox: false, mode: 'info', cwd: '/builds/grantral/e2e-tests' } } +1ms
cypress:server:args argv parsed: { _: [ '/root/.cache/Cypress/6.8.0/Cypress/Cypress' ], sandbox: false, mode: 'info', cwd: '/builds/grantral/e2e-tests', invokedFromCli: true } +2ms
cypress:server:util:proxy found proxy environment variables { npm_config_proxy: '', npm_config_https_proxy: '', npm_config_noproxy: '' } +0ms
cypress:server:args options { _: [ '/root/.cache/Cypress/6.8.0/Cypress/Cypress' ], sandbox: false, mode: 'info', cwd: '/builds/grantral/e2e-tests', invokedFromCli: true, config: {} } +1ms
cypress:server:args argv options: { _: [ '/root/.cache/Cypress/6.8.0/Cypress/Cypress' ], sandbox: false, mode: 'info', cwd: '/builds/grantral/e2e-tests', invokedFromCli: true, config: {}, testingType: 'e2e' } +0ms
cypress:server:cypress from argv [ '/root/.cache/Cypress/6.8.0/Cypress/Cypress', '--no-sandbox', '--mode=info', '--cwd', '/builds/grantral/e2e-tests' ] got options { _: [ '/root/.cache/Cypress/6.8.0/Cypress/Cypress' ], sandbox: false, mode: 'info', cwd: '/builds/grantral/e2e-tests', invokedFromCli: true, config: {}, testingType: 'e2e' } +5ms
2021-03-25T07:12:15.659Z cypress:cli child event fired { event: 'exit', code: null, signal: 'SIGABRT' }
2021-03-25T07:12:15.661Z cypress:cli child event fired { event: 'close', code: null, signal: 'SIGABRT' }
2021-03-25T07:12:15.682Z cypress:cli Stopping Xvfb
The Test Runner unexpectedly exited via a close event with signal SIGABRT
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 (Debian - 10.8)
Cypress Version: 6.8.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! e2e-tests@1.0.0 cy:info: `cypress info`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the e2e-tests@1.0.0 cy:info script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-03-25T07_12_15_706Z-debug.log

daftspaniel · 2021-03-25T16:47:27Z

We have not experienced the error since moving to Chrome for testing rather than Electron.

tkharuk · 2021-03-25T17:51:47Z

Does not happen to me anymore after upgrading to 6.5.0

LukasOchmann · 2021-04-19T12:35:57Z

I get the SIGABRT when running at least 110 tests with cypress open
OS: ubuntu-20.04.2
Browser: chrome 89/chrome 90
Cypress: 6.8.0
Node 12.20.1

prashantabellad · 2021-05-14T14:02:03Z

@jennifer-shehane the issue is still happening with electron when trying to download a pdf from aws server link. The same issue does not happen with chrome browser. I am using latest cypress version of 7.3.0 (as of today)

In this case, upon clicking download button the file download url opens in a separate browser and opens up a file location window. Could this be causing the issue?

../../third_party/electron_node/src/api/callback.cc:228:MaybeLocal<v8::Value> node::MakeCallback(v8::Isolate *, Local<v8::Object>, Local<v8::String>, int, Local<v8::Value> *, node::async_context): Assertion `(env) != nullptr' failed.
 1: 0x10a5ec805 node::Buffer::New(v8::Isolate*, char*, unsigned long, void (*)(char*, void*), void*) [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 2: 0x10a5ec61b node::Buffer::New(v8::Isolate*, char*, unsigned long, void (*)(char*, void*), void*) [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 3: 0x10a562460 node::MakeCallback(v8::Isolate*, v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*, node::async_context) [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 4: 0x107a8ae6c ElectronInitializeICUandStartNode [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 5: 0x1079853f4 ElectronInitializeICUandStartNode [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 6: 0x107983967 ElectronInitializeICUandStartNode [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 7: 0x107983820 ElectronInitializeICUandStartNode [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 8: 0x10bd34fd4 v8::internal::compiler::ZoneStats::GetCurrentAllocatedBytes() const [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 9: 0x10b9c5bd9 v8::internal::compiler::ZoneStats::GetCurrentAllocatedBytes() const [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
10: 0x10879665b v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
11: 0x107a0f96e ElectronInitializeICUandStartNode [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
12: 0x107a0f9ae ElectronInitializeICUandStartNode [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
13: 0x107a122cd ElectronInitializeICUandStartNode [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
14: 0x107a122b6 ElectronInitializeICUandStartNode [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
15: 0x107a12107 ElectronInitializeICUandStartNode [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
16: 0x1087a8bfc v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
17: 0x1087aa444 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
18: 0x1087a5c95 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
19: 0x107f92af9 electron::fuses::IsRunAsNodeEnabled() [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
20: 0x107f92823 electron::fuses::IsRunAsNodeEnabled() [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
21: 0x107f913b0 electron::fuses::IsRunAsNodeEnabled() [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
22: 0x107f91872 electron::fuses::IsRunAsNodeEnabled() [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
23: 0x1079451d8 ElectronMain [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
24: 0x1078f18c6  [/Users/prashantbellad/Library/Caches/Cypress/7.3.0/Cypress.app/Contents/MacOS/Cypress]
25: 0x7fff6af33cc9 start [/usr/lib/system/libdyld.dylib]
26: 0x7 
The Test Runner unexpectedly exited via a exit event with signal SIGABRT

charlesbrandt · 2021-07-08T21:30:43Z

I experienced this issue when running a docker container with the following configuration

test:
    image: cypress/included:7.7.0
    container_name: boilerplate_test_1
    depends_on:
      - ui
    environment:
      - DISPLAY
      # pass base url to test pointing at the web application
      - CYPRESS_baseUrl=http://boilerplate_ui_1:3000
    # share the current folder as volume to avoid copying
    working_dir: /e2e
    volumes:
      - ./:/e2e
      - /tmp/.X11-unix:/tmp/.X11-unix
      - ./web/ssl:/etc/nginx/ssl

However, on my local machine I had not run xhost local:root. Once I ran that, I stopped getting the message in this thread. Maybe a display forwarding issue?

amdcavallaro · 2021-12-13T00:08:44Z

Same issue :-(

Shahrukhk999 · 2021-12-23T12:15:40Z

got the same error after update
The Test Runner unexpectedly exited via an exit event with signal SIGABRT

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 - 20.04)
Cypress Version: 9.2.0

1Copenut · 2021-12-30T18:54:31Z

Seeing this issue with the same output as previous comment.

Platform: MacOS Big Sur latest
Cypress Version 9.1.1

mysticdevx · 2022-01-23T21:09:37Z

Hi, I am getting the error Cypress quit unexpectedly on my Mac OS(v12.1) and in terminal I read The Test Runner unexpectedly exited via an exit event with signal SIGABRT when I close the Cypress (open mode) runner window every time. I was in Cypress v8.3.1 and was not getting the error. It started appearing after upgrading to v9.3.1. Its independent of browsers, because it appears not at the end of a test run, but when the cypress is closed.

Platform: darwin-x64 (21.2.0)
Cypress Version: 9.3.1
Node version: 14.17.3

muratkeremozcan · 2022-01-25T14:26:10Z

It's a combination of Cypress and React scripts versions.

Specifically, happens when running Cypress 9.3.1 with React scripts 5+, on Mac.

Surprisingly it does not happen in CI (probably not Linux either). Renovate seamslessly updates, passes CI, we pull and SIGABIRT.

@jennifer-shehane to reproduce

git clone https://github.com/muratkeremozcan/react-hooks-in-action-with-cypress
cd react-hooks-in-action-with-cypress
# upgrade react-scripts to 5+
yarn cy:open-ct

# to work around it, use react scripts 4+

Edit: I dare say this needs a combinatorial test config.

Paste the below to https://foselab.unibg.it/ctwedge/ to generate a test configuration suite.

Instead of 3^4 tests, runs 9 test configurations to cover these kind of cryptic issues.

Profit.

Model Cypress CI
 Parameters:
   node : { A, B, C }
   cypress:  [ 1 .. 3 ]
   react-scripts : {red, green, blue}
   OS: { linux, mac, windows }

5 min read on Combinatorial Testing

thomasjm · 2022-02-23T00:41:50Z

I found that an easy way to trigger this (getting either SIGABRT or SIGILL) is to try to run multiple cypress run processes at once, in the same directory. I've tried to isolate them by setting independent values for screenshotsFolder, videosFolder, etc. but it seems like some kind of state is still shared.

This seems to happen whether I use Electron or Chrome. I turned on debug logging and noticed different messages about the browser startup, mostly the GPU. Things like "Maximum number of clients reached" and "GPU process isn't usable." So it seems like the browsers are stepping on each other somehow...

EDIT: I actually got it to perform a lot better by unsetting the DISPLAY environment variable, which seemed to be confusing Cypress even though I was running --headless.

shinusuresh · 2022-03-17T14:54:03Z

Unsetting DISPLAY in docker-compose.yml did the trick for me as well

nathan5x · 2022-05-26T22:12:21Z

Faced the same issue. Like others mentioned above, unsetting/removing DISPLAY environment variable fixes the issue. It looks like it only works when cypress open is running. I may be wrong.

luckykamon · 2022-07-10T15:23:22Z

Changing the command:
cypress run
to:
cypress run -b chrome
(change from electron to chrome) solved my problem

gopuman · 2023-08-22T16:58:19Z

Still facing the same issue. Tried with both Electron and Chrome.
Details:

┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:        12.17.4                                                                        │
  │ Browser:        Chrome 113 (headless)                                                          │
  │ Node Version:   v18.16.0 (/usr/local/bin/node)                                                 │
  │ Specs:          1 found (spec.cy.js)                                                           │
  │ Searched:       e2e/*.cy.{js,jsx,ts,tsx}                                                       │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘

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

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.

bvogel · 2023-10-10T10:33:11Z

Hi, I am getting the error Cypress quit unexpectedly on my Mac OS(v12.1) and in terminal I read The Test Runner unexpectedly exited via an exit event with signal SIGABRT when I close the Cypress (open mode) runner window every time. I was in Cypress v8.3.1 and was not getting the error. It started appearing after upgrading to v9.3.1. Its independent of browsers, because it appears not at the end of a test run, but when the cypress is closed.

Platform: darwin-x64 (21.2.0) Cypress Version: 9.3.1 Node version: 14.17.3

ever found a solution to this? Still getting this on Cypress 12

rogoit · 2023-10-27T08:26:14Z

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

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.3.3

bvogel · 2023-10-27T10:41:17Z

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

Please search Cypress documentation for possible solutions:

https://on.cypress.io

I did that beforehand (obviously) and there is nothing there.

Check if there is a GitHub issue describing this crash:

https://github.com/cypress-io/cypress/issues

Consider opening a new issue.

Why should I, here is an issue perfectly describing the problem I have, so I checked (and found an issue). Your answer does not help at all unfortunately.

a-kavka · 2024-04-10T20:11:09Z

Hi.
I am facing this issue constantly on macOS Sonoma 14.4.1 with the following details:
The Test Runner unexpectedly exited via a exit event with signal SIGKILL

Platform: darwin-arm64 (23.4.0)
Cypress Version: 13.7.2

jennifer-shehane mentioned this issue Oct 21, 2020

Node js error after run and pass test on Team City Assertion `(env) != nullptr' failed. #8863

Closed

jennifer-shehane changed the title ~~Cypress 5.4.0 - The Test Runner unexpectedly exited via a exit event with signal SIGABRT~~ Cypress 5.4.0 - The Test Runner unexpectedly exited via a exit event with signal SIGABRT - Assertion `(env) != nullptr' failed Oct 21, 2020

jennifer-shehane added the v5.4.0 🐛 Issue present since 5.4.0 label Oct 21, 2020

jennifer-shehane changed the title ~~Cypress 5.4.0 - The Test Runner unexpectedly exited via a exit event with signal SIGABRT - Assertion `(env) != nullptr' failed~~ The Test Runner unexpectedly exited via a exit event with signal SIGABRT - Assertion `(env) != nullptr' failed Oct 21, 2020

jennifer-shehane added the stage: needs information Not enough info to reproduce the issue label Oct 21, 2020

jennifer-shehane added the topic: SIG errors Program error signals, ie SIGILL, SIGSEGV, SIGBUS, SIGABRT label Nov 2, 2020

flotwig mentioned this issue Nov 20, 2020

Cypress exits with SIGABRT/SIGTERM/SIGSEGV when experimentalSourceRewriting is active. #9208

Closed

jennifer-shehane mentioned this issue Jan 27, 2021

file download not working in electron #14747

Closed

veronicamirada mentioned this issue Aug 23, 2021

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

Closed

cypress-bot bot added stage: backlog and removed stage: needs information Not enough info to reproduce the issue labels Apr 29, 2022

nagash77 added the prevent-stale mark an issue so it is ignored by stale[bot] label Apr 3, 2023

jennifer-shehane removed the stage: backlog label Nov 28, 2023

The Test Runner unexpectedly exited via a exit event with signal SIGABRT - Assertion `(env) != nullptr' failed #8865

The Test Runner unexpectedly exited via a exit event with signal SIGABRT - Assertion `(env) != nullptr' failed #8865

Comments

daftspaniel commented Oct 16, 2020 • edited by jennifer-shehane

Current behavior

Desired behavior

Test code to reproduce

Versions

jonataswalker commented Oct 19, 2020

andreasremdt commented Oct 21, 2020

jennifer-shehane commented Oct 21, 2020

andreasremdt commented Oct 21, 2020

TomaszG commented Oct 27, 2020

kamiloski commented Oct 30, 2020

daftspaniel commented Nov 3, 2020

diggabyte commented Nov 3, 2020

laurentpierson commented Nov 4, 2020

mathew-ferry13 commented Nov 6, 2020

tamaserdfalvi commented Nov 9, 2020

tkharuk commented Nov 10, 2020 • edited

hannalapitanware commented Nov 10, 2020

tamaserdfalvi commented Nov 10, 2020

jonataswalker commented Nov 10, 2020 • edited

mathew-ferry13 commented Nov 12, 2020

TomaszG commented Nov 13, 2020

Manuel-Suarez-Abascal commented Nov 13, 2020

jennifer-shehane commented Nov 17, 2020

andreasremdt commented Nov 17, 2020

vincentaudoire commented Nov 17, 2020

kamiloski commented Nov 19, 2020 • edited

jonataswalker commented Nov 24, 2020 • edited

tamaserdfalvi commented Jan 25, 2021

FromStoneage commented Jan 26, 2021

pedroAVS commented Jan 29, 2021

jennifer-shehane commented Mar 24, 2021

grantral commented Mar 25, 2021

daftspaniel commented Mar 25, 2021

tkharuk commented Mar 25, 2021

LukasOchmann commented Apr 19, 2021 • edited

prashantabellad commented May 14, 2021 • edited

charlesbrandt commented Jul 8, 2021

amdcavallaro commented Dec 13, 2021

Shahrukhk999 commented Dec 23, 2021

1Copenut commented Dec 30, 2021

mysticdevx commented Jan 23, 2022 • edited

muratkeremozcan commented Jan 25, 2022 • edited

thomasjm commented Feb 23, 2022 • edited

shinusuresh commented Mar 17, 2022

nathan5x commented May 26, 2022

luckykamon commented Jul 10, 2022

gopuman commented Aug 22, 2023

bvogel commented Oct 10, 2023

rogoit commented Oct 27, 2023

bvogel commented Oct 27, 2023 • edited

a-kavka commented Apr 10, 2024

daftspaniel commented Oct 16, 2020 •

edited by jennifer-shehane

tkharuk commented Nov 10, 2020 •

edited

jonataswalker commented Nov 10, 2020 •

edited

kamiloski commented Nov 19, 2020 •

edited

jonataswalker commented Nov 24, 2020 •

edited

LukasOchmann commented Apr 19, 2021 •

edited

prashantabellad commented May 14, 2021 •

edited

mysticdevx commented Jan 23, 2022 •

edited

muratkeremozcan commented Jan 25, 2022 •

edited

thomasjm commented Feb 23, 2022 •

edited

bvogel commented Oct 27, 2023 •

edited