Jest failing with "Call retries were exceeded", using --runInBand works-around issue
See original GitHub issue🐛 Bug Report
I’ve got 2 test files. In the test, a WebAssembly object gets instantiated. This instantiation seems to stall for some reason when running the test in CI. Locally running jest passes the tests fine.
In CI they fail with this error:
● Test suite failed to run
Call retries were exceeded
at ChildProcessWorker.initialize (../node_modules/jest-worker/build/workers/ChildProcessWorker.js:193:21)
When -i is used however, they pass as well in CI.
Jest: 24.8.0 Node: 10.15.0 Local env: macOS, 10.14.6 (18G84)) CI env: CircleCI, Docker Linux 6a7bd3b63625 4.15.0-1035-aws #37-Ubuntu SMP Mon Mar 18 16:15:14 UTC 2019 x86_64 GNU/Linux
To Reproduce
I don’t have a concise repro repo at this moment.
Expected behavior
I expect the tests to pass as well when not run in band.
Link to repl or repo (highly encouraged)
Don’t have it at this moment.
Run npx envinfo --preset jest
Paste the results here:
CI:
npx: installed 1 in 1.719s
System:
OS: Linux 4.15 Debian GNU/Linux 9 (stretch) 9 (stretch)
CPU: (36) x64 Intel(R) Xeon(R) Platinum 8124M CPU @ 3.00GHz
Binaries:
Node: 10.15.0 - ~/.nodenv/versions/10.15.0/bin/node
Yarn: 1.17.3 - /usr/bin/yarn
npm: 6.4.1 - ~/.nodenv/versions/10.15.0/bin/npm
Local:
Environment:
OS: macOS 10.14.6
Node: 10.15.0
Yarn: 1.17.3
npm: 6.4.1
Watchman: Not Found
Xcode: Xcode 10.3 Build version 10G8
Android Studio: 3.1 AI-173.4819257
Issue Analytics
- State:
- Created 4 years ago
- Reactions:59
- Comments:84 (3 by maintainers)
Top Results From Across the Web
Jest Call retries were exceeded - Stack Overflow
I got the same issue when I was running all my test cases in one go with the jest. Solution: Try running one...
Read more >hiroppy on Twitter: "Jest failing with "Call retries were ...
Jest failing with "Call retries were exceeded", using --runInBand works-around issue · Issue #8769 · facebook/jest.
Read more >Developers - Jest failing with "Call retries were exceeded", using
In the test, a WebAssembly object gets instantiated. This instantiation seems to stall for some reason when running the test in CI. Locally ......
Read more >Troubleshooting - Jest
Use this guide to resolve issues with Jest. Tests are Failing and You Don't Know Why. Try using the debugging support built into...
Read more >Error In A Basic Jest Unit Test - Unexpected Identifier - ADocLib
... SyntaxError: Unexpected token import at facebook/jest Jest failing with Call retries were exceeded using runInBand worksaround issue hot 105.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
adding
--runInBand, worked for me. I don’t know why and I don’t care as long as i see greens 🟢 🙈Meet the same issue when upgrade node from 12.13 to 16, any update on this? “jest”: “^25.5.4”, “react”: “^16.14.0”, “node”: “16”