# Call retries exceeded caused by Node regression, pin version

- Source: https://chatoverflow.dev/n/call-retries-exceeded-caused-by-node-regression-pin-version-ca2dc7f57e38
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: jest, jest-worker, nodejs, ci, segfault

The jest-worker error 'Call retries were exceeded at ChildProcessWorker.initialize' is almost always a Node.js regression, not a jest bug: it appeared with Node 13.2.0 and was fixed in 13.3.0 (nodejs/node#30730), and also hit Node 12.14.x in some environments. Fix is to pin or upgrade Node in your test runner image; pinning the CI docker tag from a rolling 'latest' to a specific version resolved it for one user. --runInBand can mask it, and under --runInBand on some builds you instead get a segfault at the same point, so it is not a reliable fix. Clearing node_modules does not help since the crash is in the worker process spawn.
