Bug: Watch mode on Linux causes a ENOSPC Node.js error

[maraisr]

Versions:

• Yarn: v0.21.3
• Node: v6.9.2
• npm: 3.10.9
• Ubuntu: 16.10

Installed using: yarn global add jest (With a chown at ~/.config/yarn/global/node_modules/)

Command failed: jest -c lib/tools/testing/jest.config.json --no-cache --watch

If I run jest -c lib/tools/testing/jest.config.json --no-cache testing works 100% fine.

Error message:

fs.js:1431
    throw error;
    ^

Error: watch /home/fooBar/dev/blah/lib/tools/testing/node_modules/core-js/modules ENOSPC
    at exports._errnoException (util.js:1022:11)
    at FSWatcher.start (fs.js:1429:19)
    at Object.fs.watch (fs.js:1456:11)
    at NodeWatcher.watchdir (/home/fooBar/.config/yarn/global/node_modules/sane/src/node_watcher.js:148:20)
    at Walker.<anonymous> (/home/fooBar/.config/yarn/global/node_modules/sane/src/node_watcher.js:361:12)
    at emitTwo (events.js:106:13)
    at Walker.emit (events.js:191:7)
    at /home/fooBar/.config/yarn/global/node_modules/walker/lib/walker.js:69:16
    at go$readdir$cb (/home/fooBar/.config/yarn/global/node_modules/graceful-fs/graceful-fs.js:149:14)
    at FSReqWrap.oncomplete (fs.js:123:15)

Tmp dir: yarn config set tmp /tmp/

Disk free space: df -h / (11% used)

Jest config: at lib/tools/testing/jest.config.json

{
	"clearMocks": true,
	"bail": true,
	"transform": {
		".(ts|tsx)": "<rootDir>/lib/tools/testing/node_modules/ts-jest/preprocessor.js"
	},
	"testResultsProcessor": "<rootDir>/lib/tools/testing/node_modules/ts-jest/coverageprocessor.js",
	"testMatch": [
		"**/__tests__/*.(ts|tsx|js)"
	],
	"moduleFileExtensions": [
		"ts",
		"tsx",
		"js"
	],
	"moduleDirectories": [
		"node_modules",
		"<rootDir>/lib/tools/testing/node_modules"
	],
	"collectCoverage": true,
	"coverageDirectory": "./reports/",
	"coverageReporters": [
		"clover",
		"lcov",
		"text-summary"
	],
	"coverageThreshold": {
		"global": {
			"branches": 50,
			"functions": 80,
			"lines": 60
		}
	},
	"collectCoverageFrom": [
		"{src,lib}/**/*.{ts,js}",
		"!lib/{tools}/**/*",
		"!**/{node_modules,vendor}/**"
	]
}

[cpojer]

This means there is no space on your drive. Please cleanup your disk.

[maraisr]

@cpojer not sure if you read the issue, but;

Disk free space: df -h / (11% used)

was mentioned in there - disk space although reported as the issue, is actually not the issue.

[maraisr]

Bump @cpojer

[zackabrah]

I am having the same issue, and there's definitely free disk space

[cpojer]

Unfortunately we do not have resources to debug this on Linux. If you have time and you could take a look and help us with a pull request to fix it, that would be greatly appreciated.

[maraisr]

@cpojer I'll take a look - but I also believe it is not limited to the Linux OS. Regardless, do you mind re-opening this issue?

[maraisr]

From my findings its not related to Jest at all. On Linux (or Mac) we have a max number of system watchers we can place at an IO level (from my understanding). So for large projects, it seems that Jest is trying to watch just way to many files.

To fix:

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Source: Node.JS Error: ENOSPC

[cpojer]

Thanks for investigating, if you install watchman, it should work.

[samit4me]

Just recently switched from Windows 7 to Ubuntu 16.04.2 LTS and Jest was working great in Windows but failed to run under Linux for the same reasons listed above. It only seems to fail if you add the --watch flag.

Firstly I took @cpojer advice and installed watchmen as per docs and ran the jest --watch again and I got the following errors:

jest --watch

events.js:163
      throw er; // Unhandled 'error' event
      ^

Error: A non-recoverable condition has triggered.  Watchman needs your help!
The triggering condition was at timestamp=1493335106: inotify-add-watch(/home/username/project_name/node_modules/browser-resolve/node_modules/resolve/example) -> The user limit on the total number of inotify watches was reached; increase the fs.inotify.max_user_watches sysctl
All requests will continue to fail with this message until you resolve
the underlying problem.  You will find more information on fixing this at
https://facebook.github.io/watchman/docs/troubleshooting.html#poison-inotify-add-watch

    at ChildProcess.<anonymous> (/home/username/project_name/node_modules/sane/node_modules/fb-watchman/index.js:207:21)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:194:7)
    at maybeClose (internal/child_process.js:899:16)
    at Socket.<anonymous> (internal/child_process.js:342:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at Pipe._handle.close [as _onclose] (net.js:510:12)
npm ERR! Test failed.  See above for more details.

This was useful as it tells you what to do, so I then used the fix from @maraisr and jest is now working on Ubuntu 🎉 🍻

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Thank you for figuring this out @maraisr @cpojer 👍 Do you think something should be added to the Jest website?

[samseralam]

Thanks Bro @maraisr

[vspedr]

@maraisr do you know if there's a sudo-less version of that solution, by any chance?

[maraisr]

@vspedr not sure - I can take a look!

But we are touching system files there, so for security you kinda need elevated permissions. If you can make yourself a sudoer i believe you can run those commands without sudo.

But yeah - i'll take a look and see what I can come up with.

[lshlyapnikov]

May be I am missing something... but why does jest need to watch anything in my node_modules directory?
How can I configure it so it skips node_modules?

[SimenB]

https://facebook.github.io/jest/docs/en/configuration.html#watchpathignorepatterns-array-string might help?

[AlexBazer]

@SimenB, as I see watchPathIgnorePatterns skips files only after watch itself is up and running, that's why the start of the watch can take a long time and sometimes can throw ENOSPC

[SimenB]

Ah, ok. A PR respecting watchPathIgnorePatterns when setting up watchers would be nice :)

[AlexBazer]

@SimenB can you please point me on the place in the source code where it directly starts watch? I have a hard time to find this place

[AlexBazer]

Find out that watcher is using HasteMap as a source of all files that should be watched, and the question right now in process of building HasteMap.
HasteMap respects modulePathIgnorePatterns option, but it's not logical to use this option based on the description from the docs:

An array of regexp pattern strings that are matched against all module paths before those paths are to be considered 'visible' to the module loader. If a given module's path matches any of the patterns, it will not be require()-able in the test environment.

am I right?

[henryemekaonuorah92]

@maraisr

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

this solution does not work on my mac os 10.13.4 it returns the error below

sysctl: illegal option -- p usage: sysctl [-bdehiNnoqx] name[=value] ... sysctl [-bdehNnoqx] -a sysctl: illegal option -- p usage: sysctl [-bdehiNnoqx] name[=value] ... sysctl [-bdehNnoqx] -a

[CodeMonkeyG]

Oh Hey @scotthovestadt! Hope you're well!

[adam-edison]

For future visitors, @pomber's solution is objectively vastly better than increasing the watch limit:

Add this to your package.json:

  "jest": {
    "modulePathIgnorePatterns": [
      "node_modules"
    ]
  }

This should be the top answer. People - please bump this. Why would you simply say "oh, out of memory/resources - give it more memory/resources" without examining the cause?

[mkahraman]

@maraisr thanks. I resolved problem. 💃

[jhanschoo]

For future visitors, @pomber's solution is objectively vastly better than increasing the watch limit:

Add this to your package.json:

  "jest": {
    "modulePathIgnorePatterns": [
      "node_modules"
    ]
  }

This should be the top answer. People - please bump this. Why would you simply say "oh, out of memory/resources - give it more memory/resources" without examining the cause?

Just a note for the record: the present proper fix didn't work until #7585 that fixed #7544 .

[tarun4all]

might be there is some permission issues try Sudo npm start

[brother-donkey]

This command will increase the number of allowed watchers:
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
Source

[JimmyBastos]

From my findings its not related to Jest at all. On Linux (or Mac) we have a max number of system watchers we can place at an IO level (from my understanding). So for large projects, it seems that Jest is trying to watch just way to many files.

To fix:

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Source: Node.JS Error: ENOSPC

@maraisr Thanks, your solution worked perfectly on Ubuntu 18.04

[sonalkrkeshri]

From my findings its not related to Jest at all. On Linux (or Mac) we have a max number of system watchers we can place at an IO level (from my understanding). So for large projects, it seems that Jest is trying to watch just way to many files.

To fix:

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Source: Node.JS Error: ENOSPC

Thanks, this resolved my issue.

[jchook]

Future visitors and @sunnykeshri @JimmyBastos @BrotherDonkey @CodeMonkeyG, for my sanity please stop propagating the watch limit fix.

For future visitors, @pomber's solution is objectively vastly better than increasing the watch limit:

Add this to your package.json:

  "jest": {
    "modulePathIgnorePatterns": [
      "node_modules"
    ]
  }

This should be the top answer. People - please bump this. Why would you simply say "oh, out of memory/resources - give it more memory/resources" without examining the cause?

[dominicfraser]

Future visitors and @sunnykeshri @JimmyBastos @BrotherDonkey @CodeMonkeyG, for my sanity please stop propagating the watch limit fix.

For future visitors, @pomber's solution is objectively vastly better than increasing the watch limit:

Add this to your package.json:

  "jest": {
    "modulePathIgnorePatterns": [
      "node_modules"
    ]
  }

This should be the top answer. People - please bump this. Why would you simply say "oh, out of memory/resources - give it more memory/resources" without examining the cause?

Create React App limits the keys that can be used within the package jest config - has anyone found a way to solve this in a CRA app?

[Mardoniosc]

From my findings its not related to Jest at all. On Linux (or Mac) we have a max number of system watchers we can place at an IO level (from my understanding). So for large projects, it seems that Jest is trying to watch just way to many files.

To fix:

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Source: Node.JS Error: ENOSPC

Thanks resovel o problema já tava procurando a horas o que era esse rro

[DrTexx]

From my findings its not related to Jest at all. On Linux (or Mac) we have a max number of system watchers we can place at an IO level (from my understanding). So for large projects, it seems that Jest is trying to watch just way to many files.

To fix:

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Source: Node.JS Error: ENOSPC

Just a note for improvement, you may be better off instructing users to check that flag/value doesn't already exist so they don't get duplicate instances of it. That or use some kind of tool for with this in mind.

[pradeepsr029]

From my findings its not related to Jest at all. On Linux (or Mac) we have a max number of system watchers we can place at an IO level (from my understanding). So for large projects, it seems that Jest is trying to watch just way to many files.

To fix:

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Source: Node.JS Error: ENOSPC

Thank you for your best answer.

[karsa87]

From my findings its not related to Jest at all. On Linux (or Mac) we have a max number of system watchers we can place at an IO level (from my understanding). So for large projects, it seems that Jest is trying to watch just way to many files.

To fix:

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Source: Node.JS Error: ENOSPC

thank yout for you answer
it's work for me

[igorgoiis]

Thanks @maraisr

[jhanschoo]

Since the last few comments have been suggesting the earlier workaround, and the later fix is starting to get buried, I feel it is necessary to reiterate for future readers (and @pradeepsrawat029 @karsa87 @igorgoiis ) that you should first try the later fix if applicable, which was originally not possible because of a jest bug:

For future visitors, @pomber's solution is objectively vastly better than increasing the watch limit:

Add this to your package.json:

  "jest": {
    "modulePathIgnorePatterns": [
      "node_modules"
    ]
  }

This should be the top answer. People - please bump this. Why would you simply say "oh, out of memory/resources - give it more memory/resources" without examining the cause?

[SlyCreator]

I was able to fix this issue with sudo react-native start

[github-actions]

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.