-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Error watching file for changes: EMFILE after clearing cache #9398
Comments
The solution to this is to install watchman through brew (wtf). I have no idea why:
Some insight would be appreciated! |
I just ran into this. I am using Jest 26.4.2 on macOS Monterey w/ M1 chip. Encountered this after upgrading from Node 12 to 16.14.2. Same exact error message as here: amasad/sane#180. |
Ganache supposedly supports Node >= v10, but we are getting some warnings when running the Ganache server in tests: Linking failure in asm.js: Unexpected stdlib member bigint: Failed to load bindings, pure JS will be used (try npm run rebuild?) This is an attempt to remove these warnings. This may cause issues when running `jest --watch`. If this does, run `brew install watchman`. See: * <jestjs/jest#9398> * <amasad/sane#180>
This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
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. |
🐛 Bug Report
After manually clearing the cache with
--clearCache
, jest is no longer able to watch files.To Reproduce
For me it happened after running
jest --config jest.config.js --clearCache --no-cache --maxWorkers=1 --coverage
through the npm script.Then
jest --watch --config jest.config.js --maxWorkers=1 --coverage
no longer works.Expected behavior
Watch to still work after clearing the cache.
envinfo
The text was updated successfully, but these errors were encountered: