-
-
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: EMFILE: too many open files #512
Comments
Did you try using the |
Please bump your ulimit |
Is there a solution for Windows? Changing the testDir in the packages.json brakes mocking. |
I was getting this error in OSX, even with ulimit set to |
@ggarnier updating to which npm version? Still trying to figure it all on Windows. |
@jberube I just ran |
@jberube , hi! npm test:
UPDtestPathDirs in config solves problem with testing node_modules by default
|
#599 is going to merge next week and it should resolve this problem too. |
I still run into this issue with ulimit=unlimited. |
For future: #8258 fixed this for me which was included in Jest 24.7.0 (I was on 24.3.1) |
I saw this issue on Jest 24.9.0, Node 13.6 and with the following ulimits:
Although the issue is completely intermittent, and might even depend on the terminal window I use (?) for example, I'm seeing it it my VSCode terminal but not my Zsh terminal 🧐 |
This worked for me, although I had to run |
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. |
I'm running jest on a limited linux box on codeanywhere and it gives me the' too many open files error".
When I'm using https://github.com/isaacs/node-graceful-fs it's just consuming all the RAM and not really working. so it get stuck on the "Using Jest CLI v0.5.4 " line.
Here is the command line log from when I'm not using node graceful-fs and running jest:
The text was updated successfully, but these errors were encountered: