Cypress: SIGSEGV after passing all tests
I can't comment on the original ticket because it's locked, but this bug https://github.com/cypress-io/cypress/issues/6458 still exists on 4.4.0 as of this evening
bwiklund
All 23 comments
@bwiklund Is your output also printing Error: This socket has been ended by the other party? If not, it may be another issue. Many things could cause a SIGSEGV error.
Could you run Cypress in debug mode mode and print the entire set of logs here?
jennifer-shehane
on 20 Apr 2020
Hi @jennifer-shehane my colleague reported https://github.com/cypress-io/cypress/issues/7073 which was closed in favour of this - can't speak for @bwiklund but with DEBUG=cypress:* the final part of my log is:
2020-04-20T16:29:09.804Z cypress:server:run attempting to close the browser
2020-04-20T16:29:09.804Z cypress:server:browsers killing browser process
2020-04-20T16:29:09.804Z cypress:server:electron-app all BrowserWindows closed, not exiting
2020-04-20T16:29:09.804Z cypress:server:browsers:electron closed event fired
2020-04-20T16:29:09.804Z cypress:server:windows removing all electron extensions []
2020-04-20T16:29:09.804Z cypress:server:preprocessor removeFile /Users/donohj03/repos/simorgh/cypress/integration/specialFeatures/cookieBanner/testsForAMPOnly.js
2020-04-20T16:29:09.804Z cypress:server:preprocessor base emitter plugin close event
2020-04-20T16:29:09.804Z cypress:server:preprocessor base emitter native close event
2020-04-20T16:29:09.804Z cypress:browserify close: /Users/donohj03/repos/simorgh/cypress/integration/specialFeatures/cookieBanner/testsForAMPOnly.js
2020-04-20T16:29:09.804Z cypress:browserify close: /Users/donohj03/repos/simorgh/cypress/integration/specialFeatures/cookieBanner/testsForAMPOnly.js
2020-04-20T16:29:09.804Z cypress:server:browsers browser process killed
2020-04-20T16:29:09.806Z cypress:server:run spec results { stats: { suites: 6, tests: 24, passes: 24, pending: 0, skipped: 0, failures: 0, wallClockStartedAt: 2020-04-20T16:28:55.805Z, wallClockEndedAt: 2020-04-20T16:29:09.766Z, wallClockDuration: 13961 }, reporter: 'spec', reporterStats: { suites: 6, tests: 24, passes: 24, pending: 0, failures: 0, start: 2020-04-20T16:28:55.816Z, end: 2020-04-20T16:29:09.799Z, duration: 13983 }, hooks: [ { hookId: 'h1', hookName: 'before each', title: [Array], body: 'function () {\n' + ' visitPage(pageType, path);\n' + ' }' }, { hookId: 'h2', hookName: 'before each', title: [Array], body: 'function () {\n' + ' visitPage(pageType, path);\n' + ' }' }, { hookId: 'h3', hookName: 'before each', title: [Array], body: 'function () {\n' + ' visitPage(pageType, path);\n' + ' }' }, { hookId: 'h4', hookName: 'before each', title: [Array], body: 'function () {\n' + '
visitPage(pageType, path);\n' + ' }' }, { hookId: 'h5', hookName: 'before each', title: [Array], body: 'function () {\n' + ' visitPage(pageType, path);\n' + ' }' }, { hookId: 'h6', hookName: 'before each', title: [Array], body: 'function () {\n' + ' visitPage(pageType, path);\n' + ' }' } ], tests: [ { testId: 'r3', title: [Array], state: 'passed', body: 'function () {\n' + " getPrivacyBanner(service, variant).should('be.visible');\n" + " getCookieBanner(service, variant).should('not.be.visible');\n" + ' getPrivacyBannerAccept(service, variant).click();\n' + " getCookieBanner(service, variant).should('be.visible');\n" + " getPrivacyBanner(service, variant).should('not.be.visible');\n" + ' getCookieBannerAccept(service, variant).click();\n' + " getCookieBanner(service, variant).should('not.be.visible');\n" + " getPrivacyBanner(service, variant).should('not.be.visible');\n" + ' }', stack: null, error: null, timings: [Object], failedFromHookId: null, wallClockStartedAt: 2020-04-20T16:28:55.816Z, wallClockDuration: 629, videoTimestamp: null }, { testId: 'r4', title: [Array], state: 'passed', body: 'function () {\n' + ' getPrivacyBannerAccept(service, variant).click();\n' + ' visitPage(pageType, path);\n' + " getPrivacyBanner(service, variant).should('be.visible');\n" + " getCookieBanner(service, variant).should('not.be.visible');\n" + ' }', stack: null, error: null, timings: [Object], failedFromHookId: null, wallClockStartedAt: 2020-04-20T16:28:56.452Z, wallClockDuration: 395, videoTimestamp: null }, { testId: 'r5', title: [Array], state: 'passed', body: 'function () {\n' + ' getPrivacyBannerAccept(service, variant).click();\n' + ' getCookieBannerAccept(service, variant).click();\n' + ' visitPage(pageType, path);\n' + " getPrivacyBanner(service, variant).should('not.be.visible');\n" + " getCookieBanner(service, variant).should('not.be.visible');\n" + ' }', stack: null, error: null, timings: [Object], failedFromHookId: null, wallClockStartedAt: 2020-04-20T16:28:56.853Z, wallClockDuration: 507, videoTimestamp: null }, { testId: 'r6', title: [Array], state: 'passed', body: 'function () {\n' + " getPrivacyBanner(service, variant).should('be.visible');\n" + " getCookieBanner(service, variant).should('not.be.visible');\n" + ' getPrivacyBannerAccept(service, variant).click();\n' + ' getCookieBannerReject(service, variant).click();\n' + ' visitPage(pageType, path);\n' + " getPrivacyBanner(service, variant).should('not.be.visible');\n" + " getCookieBanner(service, variant).should('not.be.visible');\n" + ' }', stack: null, error: null, timings: [Object], failedFromHookId: null, wallClockStartedAt: 2020-04-20T16:28:57.366Z, wallClockDuration: 1490, videoTimestamp: null }, { testId: 'r8', title: [Array], state: 'passed', body: 'function () {\n' + " getPrivacyBanner(service, variant).should('be.visible');\n" + " getCookieBanner(service, variant).should('not.be.visible');\n" + ' getPrivacyBannerAccept(service, variant).click();\n' + " getCookieBanner(service, variant).should('be.visible');\n" + " getPrivacyBanner(service, variant).should('not.be.visible');\n" + ' getCookieBannerAccept(service, variant).click();\n' + " getCookieBanner(service, variant).should('not.be.visible');\n" + " getPrivacyBanner(service, variant).should('not.be.visible');\n" + ' }', stack: null, error: null, timings: [Object], failedFromHookId: null, wallClockStartedAt: 2020-04-20T16:28:58.864Z, wallClockDuration: 357, videoTimestamp: null }, { testId: 'r9', title: [Array], state: 'passed', body: 'function () {\n' + ' getPrivacyBannerAccept(service, variant).click();\n' + ' visitPage(pageType, path);\n' + " getPrivacyBanner(service, variant).should('be.visible');\n" + " getCookieBanner(service, variant).should('not.be.visible');\n" + ' }', stack: null, error: null, timings: [Object], failedFromHookId: null, wallClockStartedAt: 2020-04-20T16:28:59.227Z, wallClockDuration: 302, videoTimestamp: null }, { testId: 'r10', title: [Array], state: 'passed', body: 'function () {\n' + ' getPrivacyBannerAccept(service, variant).click();\n' + ' getCookieBannerAccept(service, variant).click();\n' + ' visitPage(pageType, path);\n' + " getPrivacyBanner(service, variant).should('not.be.visible');\n" + " getCookieBanner(service, variant).should('not.be.visible');\n" + ' }', stack: null, error: null, timings: [Object], failedFromHookId: null, wallClockStartedAt: 2020-04-20T16:28:59.536Z, wallClockDuration: 368, videoTimestamp: null }, { testId: 'r11', title: [Array], state: 'passed', body: 'function () {\n' + " getPrivacyBanner(service, variant).should('be.visible');\n" + " getCookieBanner(service, variant).should('not.be.visible');\n" + ' getPrivacyBannerAccept(service, variant).click();\n' + ' getCookieBannerReject(service, variant).click();\n' + ' visitPage(pageType, path);\n' + " getPrivacyBanner(service, variant).should('not.be.visible');\n" + " getCookieBanner(service, variant).should('not.be.visible');\n" + ' }', stack: null, error: null, timings: [Object], failedFromHookId: null, wallClockStartedAt: 2020-04-20T16:28:59.910Z, wallClockDuration: 574, videoTimestamp: null }, { testId: 'r13', title: [Array], state: 'passed', body: 'function () {\n' + " getPrivacyBanner(service, variant).should('be.visible');\n" + " getCookieBanner(service, variant).should('not.be.visible');\n" + ' getPrivacyBannerAccept(service, variant).click();\n' + " getCookieBanner(service, variant).should('be.visible');\n" + " getPrivacyBanner(service, variant).should('not.be.visible');\n" + ' getCookieBannerAccept(service, variant).click();\n' + " getCookieBanner(service, variant).should('not.be.visible');\n" + " getPrivacyBanner(service, variant).should('not.be.visible');\n" + ' }', stack: null, error: null, timings: [Object], failedFromHookId: null, wallClockStartedAt: 2020-04-20T16:29:00.490Z, wallClockDuration: 948, videoTimestamp: null }, { testId: 'r14', titl────────────────────────────────────────────────────────────────────────────────────────────────────
Running: specialFeatures/cookieBanner/testsForCanonicalOnly.js (14 of 14)
cypress:cli child event fired { event: 'exit', code: null, signal: 'SIGSEGV' } +2m
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 (18.7.0)
Cypress Version: 4.4.0
I can share the whole file if you let me know the best way to do this. Thanks!
jamesdonoh
on 20 Apr 2020
@jamesdonoh Yeah, your SIGSEGV doesn't look to be logged after all the tests are run, but in between one spec before starting a new spec. The log of course gives no helpful information :(
jennifer-shehane
on 21 Apr 2020
@jennifer-shehane is there anything else we can do to help diagnose the cause of this please? The issue we reported above was closed as a dupe of this one, and since migrating to 4.4.0 70-80% of our test runs now crash in this way.
jamesdonoh
on 22 Apr 2020
@jennifer-shehane is there anything else we can do to help diagnose the cause of this please? The issue we reported above was closed as a dupe of this one, and since migrating to 4.4.0 70-80% of our test runs now crash in this way.
Still seeing these crashed on 4/5 of our test runs. We upgraded to cypress 4.4.0 to move away from a security vulnerability in an older version and are reluctant to rollback re-introducing that security vuln.
Any updates would be appreciated.
chris-hinds
on 24 Apr 2020
Just adding another report that the SIGSEGV is happening, with no useful log at all.
marinakuranda
on 24 Apr 2020
Hi,
We have the same issue here, reproduced with a minimal single test:
describe('My First Test', () => {
it('Visits the home', () => {
cy.visit('/');
});
});
cypress.json file is completely empty:
{}
Ran either in (gitlab-)ci with cypress/included docker image, or directly from the project root with this command on Mac OS Catalina:
CYPRESS_BASE_URL=http://localhost:3000 npx run cypress
Executed cypress version was 4.4.1, but we've encountered this issue since at least 4.1.0.
The error with DEBUG log activated is similar to what was previously indicated:
cypress:cli child event fired { event: 'exit', code: null, signal: 'SIGSEGV' } +13s
The Test Runner unexpectedly exited via a exit event with signal SIGSEGV
Also note that we sometimes got the SIGBUS error instead:
cypress:cli child event fired { event: 'exit', code: null, signal: 'SIGBUS' } +13s
The Test Runner unexpectedly exited via a exit event with signal SIGBUS
I then ran the following command:
DEBUG=* CYPRESS_BASE_URL=https://www.google.com npx cypress run
10 times out of 10, the result was a success by targeting the google.com home page rather than our own app.
Our web app renders much more slowly than the google.com home page, with quite a lot of javascript executed on the client side (8-10 seconds before first interactivity).
Hope this helps narrow down the problem.
Of course we are working on making our app faster (but don't have control over all scripts, and need to be able to run cypress while the app is in development mode, which is slower).
Is there a workaround to increase the limit (time / memory), for resource heavy web apps?
It used to work 100% well with more tests in cypress 3, so maybe performance or tolerance was impacted with version 4?
apascal
on 27 Apr 2020
Same problem seems to happen for me, in 4.5.0:
================================================================================
(Run Finished)
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 (Debian - 10.3)
Cypress Version: 4.5.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
abzainuddin
on 3 May 2020
yeah.... same problem in our CI:
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 (Ubuntu Linux - 18.04)
Cypress Version: 4.5.0
edsadr
on 7 May 2020
Platform: linux (Debian - 8.10)
--
612 | Cypress Version: 4.5.0
613 | at /codebuild/output/src145582674/src/node_modules/cypress/lib/errors.js:326:15
614 | at tryCatcher (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/util.js:16:23)
615 | at Promise._settlePromiseFromHandler (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/promise.js:547:31)
616 | at Promise._settlePromise (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/promise.js:604:18)
617 | at Promise._settlePromise0 (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/promise.js:649:10)
618 | at Promise._settlePromises (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/promise.js:729:18)
619 | at Promise._fulfill (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/promise.js:673:18)
620 | at Promise._resolveCallback (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/promise.js:466:57)
621 | at Promise._settlePromiseFromHandler (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/promise.js:559:17)
622 | at Promise._settlePromise (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/promise.js:604:18)
623 | at Promise._settlePromise0 (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/promise.js:649:10)
624 | at Promise._settlePromises (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/promise.js:729:18)
625 | at Promise._fulfill (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/promise.js:673:18)
626 | at Promise._resolveCallback (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/promise.js:466:57)
627 | at Promise._settlePromiseFromHandler (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/promise.js:559:17)
628 | at Promise._settlePromise (/codebuild/output/src145582674/src/node_modules/cypress/node_modules/bluebird/js/release/promise.js:604:18) known: true }
629 | ·[?25h
mwren-mshanken
on 12 May 2020
Same here using v4.5.0. Our specs pass locally but on Travis-CI fail after 2 minutes of the initial specs passing with:
The Test Runner unexpectedly exited via a exit event with signal SIGSEGV
After restarting the Travis build about 3 times it will complete successfully.
Cypress 4.3 passes every time no problem.
We are using cypress with TypeScript and no plugins. We are using fixtures only with quite a heavy API.
cypress.json:
{
"supportFile": "cypress/support/index.ts",
"videoUploadOnPasses": false,
"baseUrl": "http://localhost:3030/_",
"env": {
"apiUrl": "http://localhost:3000/api/v2/"
}
}
On Travis we're using a VM with 7.5Gb memory, no docker.
Travis config:
dist: xenial
language: node_js
node_js: 10
addons:
chrome: stable
cache:
yarn: true
directories:
- node_modules
env:
- NODE_OPTIONS="--max_old_space_size=6144" # ensure enough memory for the tests
before_install:
- curl -o- -L https://yarnpkg.com/install.sh | bash
- export PATH=$HOME/.yarn/bin:$PATH
before_script:
- yarn start --silent &
script:
- set -e # Exit immediately if a subsequent command fails
- yarn install --non-interactive --production=false --pure-lockfile
- cypress install && yarn cypress run --config video=false
- kill $(jobs -p) || true
jboler
on 18 May 2020
With Cypress 4.6 the tests all complete but the Cypress process locks up logging the final output:
jboler
on 21 May 2020
Still failing with v4.8
jboler
on 15 Jun 2020
So we did these 3 things and our Travis Cypress runs no longer hang. Not sure which one fixed it but I suspect it's the file watching because it's a very large codebase.
- Upgraded to Cypress 5.1
- Removed
@cypress/webpack-preprocessorfrom package.json - Disabled file events watchers for both cypress and our React app dev server with this:
.travis.yml - Added --config watchForFileChanges=false
- cypress install && yarn cypress run --config watchForFileChanges=false
craco.config.js - added this:
...(process.env.CI && {
devServer: {
watchOptions: {
ignored: '/**',
},
},
}),
Hi all... looks like I'm joining the party with this crash:
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: 5.1.0
I saved my changes which triggered the test to run again as I still had the test browser open from the previous test. This happened to me twice in a span of 5 minutes :(
markodelgadillo
on 12 Sep 2020
Cypress: 5.4.0
Browser: Chrome 86
OS: CentOS 7.8.2003
✔ All specs passed! 00:04 20 20 - - -
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: linux (CentOS - 7.8.2003)
Cypress Version: 5.4.0
at /data/cypress/node_modules/cypress/lib/errors.js:346:15
at tryCatcher (/data/cypress/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/data/cypress/node_modules/bluebird/js/release/promise.js:547:31)
at Promise._settlePromise (/data/cypress/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/data/cypress/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/data/cypress/node_modules/bluebird/js/release/promise.js:729:18)
at Promise._fulfill (/data/cypress/node_modules/bluebird/js/release/promise.js:673:18)
at Promise._resolveCallback (/data/cypress/node_modules/bluebird/js/release/promise.js:466:57)
at Promise._settlePromiseFromHandler (/data/cypress/node_modules/bluebird/js/release/promise.js:559:17)
at Promise._settlePromise (/data/cypress/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/data/cypress/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/data/cypress/node_modules/bluebird/js/release/promise.js:729:18)
at Promise._fulfill (/data/cypress/node_modules/bluebird/js/release/promise.js:673:18)
at Promise._resolveCallback (/data/cypress/node_modules/bluebird/js/release/promise.js:466:57)
at Promise._settlePromiseFromHandler (/data/cypress/node_modules/bluebird/js/release/promise.js:559:17)
at Promise._settlePromise (/data/cypress/node_modules/bluebird/js/release/promise.js:604:18) {
known: true
}
Tests are run via API and work perfectly on Cypress 5.3.0
UPDATE
After updating to 5.5.0, the error didn't disappear. But there are no errors on Windows 10 with the same tests and configurations.
lexsmil
on 17 Oct 2020
Hi @jennifer-shehane I have encountered the same issue after upgrading from 5.3.0 to the latest 5.4.0 even with all tests passing. I use the docker image cypress/browsers:node12.14.1-chrome85-ff81.
2020-10-22T19:41:52.478Z cypress:server:cypress about to exit with code 0
2020-10-22T19:41:52.478Z cypress:rewriter:threads intercepted process.exit called, closing worker threads
2020-10-22T19:41:52.485Z cypress:rewriter:threads worker exited { exitCode: 0, worker: { isBusy: false, id: 4, freeWorkers: 4 } }
2020-10-22T19:41:52.498Z cypress:rewriter:threads worker exited { exitCode: 0, worker: { isBusy: false, id: 2, freeWorkers: 3 } }
2020-10-22T19:41:52.498Z cypress:rewriter:threads worker exited { exitCode: 0, worker: { isBusy: false, id: 3, freeWorkers: 2 } }
2020-10-22T19:41:52.518Z cypress:rewriter:threads worker exited { exitCode: 0, worker: { isBusy: false, id: 1, freeWorkers: 1 } }
2020-10-22T19:41:52.555Z cypress:https-proxy received error on client browserSocket { err: Error: write EPIPE at afterWriteDispatched (internal/stream_base_commons.js:154:25) at writeGeneric (internal/stream_base_commons.js:145:3) at Socket._writeGeneric (net.js:784:11) at Socket._write (net.js:796:8) at doWrite (_stream_writable.js:403:12) at writeOrBuffer (_stream_writable.js:387:5) at Socket.Writable.write (_stream_writable.js:318:11) at Socket.ondata (_stream_readable.js:695:22) at Socket.emit (events.js:310:20) at addChunk (_stream_readable.js:286:12) at readableAddChunk (_stream_readable.js:268:9) at Socket.Readable.push (_stream_readable.js:209:10) at TCP.onStreamRead (internal/stream_base_commons.js:186:23) { errno: 'EPIPE', code: 'EPIPE', syscall: 'write' }, url: 'example.com:443' }
2020-10-22T19:41:52.619Z cypress:rewriter:threads all workers terminated, exiting for real
2020-10-22T19:41:52.753Z cypress:cli child event fired { event: 'exit', code: null, signal: 'SIGSEGV' }
2020-10-22T19:41:52.760Z cypress:cli Stopping Xvfb
2020-10-22T19:41:52.767Z cypress:cli child event fired { event: 'close', code: null, signal: 'SIGSEGV' }
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 (Debian - 10.2)
Cypress Version: 5.4.0
yunj
on 22 Oct 2020
Commenting here as my post was closed as a duplicate, the same issue is occuring in our CI and local environments to error unexpectedly after all tests have passed successfully. We are using Cypress 5.4.0 running in headless mode for E2E testing.
This is screenshot of local run failing with debug,
AntonioGargaro
on 2 Nov 2020
Also crashes even though all spec is passed in the bitbucket pipeline. I have no problem with a crash, but this crash makes my test run failed even though all passed.
At my local also crash like this.
cupidline
on 3 Nov 2020
SOLUTION: Cypress version 5.6.0 in MacOS, when running through terminal, after all the tests complete, cypress crashes and I am getting the same error: The Test Runner unexpectedly exited via a exit event with signal SIGSEGV
I found the reason. the entry "experimentalSourceRewriting": true in the Cypress.json file causes the problem. when removed everything works like a charm. No error on terminal. Hope it works for you all
mysticdevx
on 15 Nov 2020
@mysticdevx Are you able to provide a reproducible example? Even one you can email to [email protected] would be helpful. We'd really like to track down this blocking issue and this is an interesting situation you've mentioned.
jennifer-shehane
on 16 Nov 2020
@mysticdevx Are you able to provide a reproducible example? Even one you can email to [email protected] would be helpful. We'd really like to track down this blocking issue and this is an interesting situation you've mentioned.
SigsegvReproduceRepo
pushed a very basic project having one test and only experimentalSourceRewriting property in Cypress.json along with very brief reproduce steps. Mailed too.
mysticdevx
on 16 Nov 2020
@mysticdevx Thanks for providing this example. This led one of our engineers to open an issue specific to the experimentalSourceRewriting flag bug.
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. https://github.com/cypress-io/cypress/issues/9208
We don't believe this is the issue for everyone in this thread however, since this issue was opened before experimentalSourceRewriting was released, so we will leave this issue open to track the cause of any other SIGSEGV errors.
jennifer-shehane
on 17 Nov 2020
Related issues
stormherz
·
3Comments
simonhaenisch
·
3Comments
brian-mann
·
3Comments
weskor
·
3Comments
rbung
·
3Comments
Most helpful comment
Also crashes even though all spec is passed in the bitbucket pipeline. I have no problem with a crash, but this crash makes my test run failed even though all passed.
At my local also crash like this.