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.

Cypress Crashes w/ SIGSEGV Error in CircleCI w/ Parallelism

See original GitHub issue

Current behavior

When running a workflow in CircleCI with a Cypress job, one or more of the containers will crash with a SIGSEGV error during the test run. This happens sometimes mid run and sometimes at the end of the run after all tests have passed. Attached are a screenshot fo the output in CircleCI as well as the DEBUG logs from the cypress run in CircleCI. This is happening a lot more frequently since we upped our parallelism in CircleCI to 3 from 2. Screenshot1 Screenshot2 CircleCI Cypress Logs.txt.zip

Desired behavior

Cypress should not crash and/or send SIGSEGV error during CircleCI run with parallelism

Test code to reproduce

Happening for our entire project and not able to share repo/code

Versions

Tests are running on the latest version of Cypress at this time (6.4.0) and on the latest version of Chrome. CircleCI is using a Docker Medium executor and the following images: circleci/ruby:2.5.8-node-browsers, circleci/mysql:5.7.24, cypress/base:14.7.0

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:12 (1 by maintainers)

Top GitHub Comments

1reaction

pkyeckcommented, Feb 17, 2021

@jonstone904 I’ve always disabled video-creation on the CI server. So no luck there … Just tried re-running the test via SSH but they passed without error three times 😦 Now updated cypress from 6.2.1 -> 6.5.0 and will check again.

0reactions

pkyeckcommented, Mar 25, 2021

@jonstone904 thanks for the update.

As I mentioned above, after downgrading these errors went away. I sometimes get the “maxListener” errors and tests randomly fail – but this seems be a different problem. I currently don’t have the time to test the newest version with a higher resource class.

But please update the issue if this turns out to be a solution to the problem. Thanks again

Top Results From Across the Web

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

cypress-io/cypress - CircleCI Developer Hub

Runs all Cypress component tests without recording results on the Dashboard. Installs dependencies with "npm ci", caches NPM modules and Cypress ...

CircleCI Parallelism As A Parameter - Gleb Bahmutov

First, the install job runs, then the test job uses the workspace with the source code and the installed dependencies to start the...

Continuous Integration - cypress - w3resource

The problem with this is that if the server takes time to boot, ... Cypress is able to run tests in parallel across...