Segmentation fault (core dumped) on Github Actions running Node.js 12.x #10662

Ionaru · 2020-10-20T15:57:27Z

🐛 Bug Report

Running tests on Github Actions using Node.js 12.x gives a segmentation fault very frequently when the tests are done.

To Reproduce

Steps to reproduce the behavior:

Create jest tests
Create Github workflow to test on Node.js 12.x
Run the workflow

Expected behavior

The tests succeed (or fail) normally.

Link to repl or repo (highly encouraged)

https://github.com/Ionaru/typeorm-utils/runs/1281969729?check_suite_focus=true

envinfo

  System:
    OS: Linux 5.4 Ubuntu 18.04.5 LTS (Bionic Beaver)
    CPU: (2) x64 Intel(R) Xeon(R) Platinum 8171M CPU @ 2.60GHz
  Binaries:
    Node: 12.19.0 - /opt/hostedtoolcache/node/12.19.0/x64/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 6.14.8 - /opt/hostedtoolcache/node/12.19.0/x64/bin/npm
  npmPackages:
    jest: ^26.6.0 => 26.6.0

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

Ref: jestjs/jest#10662

seahindeniz · 2021-06-19T10:34:31Z

Similar issue also happens with Node 16.x
The one problem is that, using jest with pnpm or yarn result in fail ~~but not with npm 🙃~~

Here is the minimal repo with three package manager setup on different branches
https://github.com/seahindeniz/jest-issue-10662

Screenshots

.

npm:

pnpm:

yarn:

Windows 10, Node 16.3.0

seahindeniz · 2021-06-19T10:44:57Z

Seems like it fails with npm as well on GitHub Actions https://github.com/seahindeniz/jest-issue-10662/runs/2864518775?check_suite_focus=true

EmiM · 2021-06-29T13:06:56Z

We also experienced this problem. We sometimes get segmentation fault (core dumped) after all tests (and other jobs) pass:
https://github.com/ZbayApp/waggle/pull/53/checks?check_run_id=2942073718

ubuntu-20.04
node 12

EmiM · 2021-06-29T15:30:22Z

I removed --collectCoverage and it passed so it probably caused the error.

Jolg42 · 2021-07-08T17:08:08Z

Also getting Segmentation fault (core dumped) 3 times in 3 days, it was extremely rare before.
https://github.com/prisma/prisma/runs/3021367125#step:9:247

Probably the latest Node.js 12.x version got a glitch?

millsp · 2021-07-08T17:45:28Z

And a fourth time https://github.com/prisma/prisma/runs/3021589039#step:9:246

mhf-ir · 2021-07-18T11:08:32Z

Same problem docker node:16-buster-slim, switch to node:15-buster-slim problem solve, might be clue

Jolg42 · 2021-07-27T13:34:18Z

Switching to node:14-buster or node:12-buster also solved it.

TrySound · 2021-09-21T10:32:03Z

I just solved the problem by setting maxWorkers to 3.

I have a guess experimental-vm-modules flag spends one more available worker and jest-worker must use os.CPUS - 2 or something like this.

cc @SimenB

Should still dodge the weird GH issue tracked by jestjs/jest#10662 but won't impact local machine runs as much

Removed the native directory. Made the tests run expecting the same structure as what we distribute. That same structure is created by either running `yarn compile` or `node-pre-gyp install` (the second being how and end user gets the binary). The publish structure is the same other than the new entry point, so that should continue working. * Add NAPI to changelog, would be good to remember * bump-version: Set release version 0.8.0-pre.1 * Add a comment to clarify where changes happen Limited jest `maxWorkers` to dodge the weird GH issue tracked by jestjs/jest#10662 but won't impact local machine runs as much Co-authored-by: Leeroy Travis <[email protected]>

* Update to latest of all deps * Recrypt 0.12 * Try Node 16 as well * Reduce cardinality * Bump MSRV to 1.51 * Update documentation. * Upgrade JS dependencies too. * Replace Node 10 with 16 in the matrix * Apply patch * Update recrypt * And changelog * Rust 2021 so we can use recrypt 0.13 * Checkpointing migration to NAPI * Try different coverage switch command * Rust fmt * Neon packaging (#75) Removed the native directory. Made the tests run expecting the same structure as what we distribute. That same structure is created by either running `yarn compile` or `node-pre-gyp install` (the second being how and end user gets the binary). The publish structure is the same other than the new entry point, so that should continue working. * Add NAPI to changelog, would be good to remember * bump-version: Set release version 0.8.0-pre.1 * Add a comment to clarify where changes happen Limited jest `maxWorkers` to dodge the weird GH issue tracked by jestjs/jest#10662 but won't impact local machine runs as much Co-authored-by: Leeroy Travis <[email protected]> Co-authored-by: Murph Murphy <[email protected]> Co-authored-by: Leeroy Travis <[email protected]>

Refs: jestjs/jest#10662 (comment)

AlexMesser · 2022-08-15T17:23:45Z

Having the same issue with node:16.14.0 + --experimental-vm-modules flag. Tests successfully passed on the local machine but fails on GitHub Actions with Segmentation fault (core dumped) error.

Setting maxWorkers to 3-4-5 causes tests to stuck.
Setting --runInBand flag causes fail on a local machine with segmentation fault npm test error.

adico1 · 2022-08-26T11:35:38Z

in my case, not related to node 12,
removing --detectOpenHandles helped

reference: https://stackoverflow.com/questions/68012814/gitlab-jest-test-segmentation-fault-core-dumped

dgrisham · 2022-08-31T21:06:42Z

Haivng this issue as well running tests on the node:16-alpine container -- the tests were working fine previously, and now the same tests fail during the setup phase. They run fine locally with the same configuration. Same issue with node 18, and we can't go below 16 with our dependencies

Getting segmentation fault error on GitHub CI too frequently for running tests with coverage. trying possible fix for it Reference: jestjs/jest#10662

chirag-madlani · 2022-10-12T13:33:50Z

Hi all,
I am facing the same issue with my project below is the config that we are using.

Ubuntu version: 20.04.05 LTS
frontend-maven-plugin - v1.11.0
nodeVersion - v16.14.2
yarnVersion - v1.22.18

Getting this error while running Unit tests via jest

jest --passWithNoTests --coverage

Tried running --coverage but that didn't help

Let me know if there's a workaround or any debug technique that I can use

* fix(ui-test): segmentation fault error unit tests Getting segmentation fault error on GitHub CI too frequently for running tests with coverage. trying possible fix for it Reference: jestjs/jest#10662 * fix failed unit tests * remove coverage to test segmentation fault * update maxWorker to resolve segmentation fault * remove duplicate key from props

* fix(ui-test): segmentation fault error unit tests Getting segmentation fault error on GitHub CI too frequently for running tests with coverage. trying possible fix for it Reference: jestjs/jest#10662 * fix failed unit tests * remove coverage to test segmentation fault * update maxWorker to resolve segmentation fault * remove duplicate key from props (cherry picked from commit 2349684)

* Release 0.12.3 - Updated the required files * updated Docker File * fix(ui-test): segmentation fault error unit tests (#7840) * fix(ui-test): segmentation fault error unit tests Getting segmentation fault error on GitHub CI too frequently for running tests with coverage. trying possible fix for it Reference: jestjs/jest#10662 * fix failed unit tests * remove coverage to test segmentation fault * update maxWorker to resolve segmentation fault * remove duplicate key from props (cherry picked from commit 2349684) Co-authored-by: Chirag Madlani <[email protected]>

KittySparkles · 2023-02-05T11:58:39Z

So this is going to sound super weird, but for me the problem started occurring when I upgraded isomorphic-unfetch to v4+. I’ve been having this segfault problem for about 2 weeks, and eventually tracked back the first occurrence to the Dependabot PR updating isomorphic-unfetch in my project. I tried rolling back isomorphic-unfetch to v3.1.0, and Jest no longer throws a segfault. I have no clue why that would be the problem though.

lucasrodriguezdavila · 2023-04-07T01:04:39Z

v3.1.0,

this solved for me, thanks

github-actions · 2023-09-16T07:12:21Z

As noted in the Bug Report template, all bug reports requires a minimal reproduction. Please open up a new issue providing one. Read more at https://stackoverflow.com/help/minimal-reproducible-example.

github-actions · 2023-10-17T00:10:03Z

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

Ionaru added Bug Report Needs Repro Needs Triage labels Oct 20, 2020

Ionaru added a commit to Ionaru/typeorm-utils that referenced this issue Oct 23, 2020

Disable testing on Node.js 12 temporarily.

5d200d6

Ref: jestjs/jest#10662

EmiM mentioned this issue Jun 29, 2021

CI - npm test throws Segmentation fault (core dumped) sometimes TryQuiet/waggle#58

Closed

MuckT mentioned this issue Oct 12, 2021

Update to @testing-library/react-native and add @testing-library/jest-native valora-inc/wallet#1184

Merged

skeet70 added a commit to IronCoreLabs/recrypt-node-binding that referenced this issue Dec 6, 2021

Try a different maxWorkers setting

5639968

Should still dodge the weird GH issue tracked by jestjs/jest#10662 but won't impact local machine runs as much

skeet70 mentioned this issue Dec 6, 2021

Upgrade dependencies IronCoreLabs/recrypt-node-binding#74

Merged

trivikr mentioned this issue Jan 6, 2022

test(package.json): use lerna run test in test:all aws/aws-sdk-js-v3#3148

Closed

trivikr added a commit to trivikr/aws-sdk-js-v3 that referenced this issue Jan 6, 2022

fix: disable jest coverage to test seg fault

9122129

Refs: jestjs/jest#10662 (comment)

skeet70 mentioned this issue Jan 15, 2022

First pass at adding arm64 to the build. IronCoreLabs/recrypt-node-binding#77

Merged

SimenB removed the Needs Repro label Feb 17, 2022

0x2b3bfa0 mentioned this issue Jun 8, 2022

Integrate cml publish with cml send-comment iterative/cml#1026

Merged

8 tasks

davidmurdoch mentioned this issue Jul 26, 2022

Segfaulting and exiting with 1... trufflesuite/ganache#3428

Open

chirag-madlani mentioned this issue Oct 1, 2022

fix(ui-test): segmentation fault error unit tests open-metadata/OpenMetadata#7840

Merged

5 tasks

ceifa mentioned this issue Dec 11, 2022

npm test Segmentation fault ceifa/wasmoon#65

Closed

ashley-evans mentioned this issue Dec 30, 2022

Feature/555 deploy dry run ashley-evans/how-many-buzzwords#556

Merged

nolanlawson mentioned this issue Jan 22, 2023

chore: remove @babel/preset-env nolanlawson/emoji-picker-element#317

Closed

bourgeoa mentioned this issue Mar 1, 2023

autocompleteField tests fail with latest [email protected] SolidOS/solid-ui#528

Open

SimenB added the Needs Reproduction Every bug report requires a minimal reproduction label Sep 16, 2023

github-actions bot closed this as completed Sep 16, 2023

github-actions bot locked as resolved and limited conversation to collaborators Oct 17, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Segmentation fault (core dumped) on Github Actions running Node.js 12.x #10662

Segmentation fault (core dumped) on Github Actions running Node.js 12.x #10662

Ionaru commented Oct 20, 2020 •

edited

Loading

seahindeniz commented Jun 19, 2021 •

edited

Loading

seahindeniz commented Jun 19, 2021

EmiM commented Jun 29, 2021

EmiM commented Jun 29, 2021

Jolg42 commented Jul 8, 2021

millsp commented Jul 8, 2021

mhf-ir commented Jul 18, 2021

Jolg42 commented Jul 27, 2021

TrySound commented Sep 21, 2021

AlexMesser commented Aug 15, 2022

adico1 commented Aug 26, 2022 •

edited

Loading

dgrisham commented Aug 31, 2022

chirag-madlani commented Oct 12, 2022

KittySparkles commented Feb 5, 2023 •

edited

Loading

lucasrodriguezdavila commented Apr 7, 2023

github-actions bot commented Sep 16, 2023

github-actions bot commented Oct 17, 2023

Segmentation fault (core dumped) on Github Actions running Node.js 12.x #10662

Segmentation fault (core dumped) on Github Actions running Node.js 12.x #10662

Comments

Ionaru commented Oct 20, 2020 • edited Loading

🐛 Bug Report

To Reproduce

Expected behavior

Link to repl or repo (highly encouraged)

envinfo

seahindeniz commented Jun 19, 2021 • edited Loading

seahindeniz commented Jun 19, 2021

EmiM commented Jun 29, 2021

EmiM commented Jun 29, 2021

Jolg42 commented Jul 8, 2021

millsp commented Jul 8, 2021

mhf-ir commented Jul 18, 2021

Jolg42 commented Jul 27, 2021

TrySound commented Sep 21, 2021

AlexMesser commented Aug 15, 2022

adico1 commented Aug 26, 2022 • edited Loading

dgrisham commented Aug 31, 2022

chirag-madlani commented Oct 12, 2022

KittySparkles commented Feb 5, 2023 • edited Loading

lucasrodriguezdavila commented Apr 7, 2023

github-actions bot commented Sep 16, 2023

github-actions bot commented Oct 17, 2023

Ionaru commented Oct 20, 2020 •

edited

Loading

seahindeniz commented Jun 19, 2021 •

edited

Loading

adico1 commented Aug 26, 2022 •

edited

Loading

KittySparkles commented Feb 5, 2023 •

edited

Loading