Jest stuck - keeps spinning, no output
See original GitHub issueEnvironment
- 
node -v: v6.10.3
- 
npm -v: 3.10.10
- 
npm ls react-scripts(if you haven’t ejected): `-- (empty) npm ERR! code 1
- 
Operating system: Windows 
Steps to Reproduce
No matter if start my project, or stop/start Jest - it keeps spinning and does nothing. One of five it suddenly works, then gets stuck again after a while.
There are some warnings in the developer console:

Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:16 (6 by maintainers)
 Top Results From Across the Web
Top Results From Across the Web
node.js - jest hangs indefinitely, runs no tests - Stack Overflow
On MacOS I fixed this by uninstalling and reinstalling watchman using brew uninstall watchman and then reinstalling with brew install watchman .
Read more >Troubleshooting - Jest
Troubleshooting. Uh oh, something went wrong? Use this guide to resolve issues with Jest. Tests are Failing and You Don't Know Why.
Read more >Introduction: Troubleshooting - Wallaby.js
Ensure tests are passing outside of Wallaby · Diagnostics Report · More debug information · Configuration issue · Try resetting your testing framework...
Read more >Tidal locking - Wikipedia
Alternative names for the tidal locking process are gravitational locking, captured rotation, and spin–orbit locking. Tidal locking results in the Moon rotating ...
Read more >Testing Vite with minimal config using Vitest - LogRocket Blog
Also, we're configuring our test suite without considering the app itself. You might have a better time configuring Jest if your website already ......
Read more > Top Related Medium Post
Top Related Medium Post
No results found
 Top Related StackOverflow Question
Top Related StackOverflow Question
No results found
 Troubleshoot Live Code
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
Top Related Reddit Thread
No results found
 Top Related Hackernoon Post
Top Related Hackernoon Post
No results found
 Top Related Tweet
Top Related Tweet
No results found
 Top Related Dev.to Post
Top Related Dev.to Post
No results found
 Top Related Hashnode Post
Top Related Hashnode Post
No results found

Probably related to https://github.com/facebook/jest/issues/4419, try creating a git repo inside or waiting until the fix is released. At least this fixed it for me.
I’m not convinced that the module resolution is the root cause. This minimal repo worked OK. 😕 The only time it I got the “testing changes” spinner was before setting up a
gitrepo and getting theError: This promise must be present when running with -o.error from #142.