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.

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

See original GitHub issue

🐛 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

Issue Analytics

State:
Created 3 years ago
Reactions:20
Comments:13 (1 by maintainers)

Top GitHub Comments

6reactions

TrySoundcommented, Sep 21, 2021

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

1reaction

dgrishamcommented, Aug 31, 2022

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