-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Cypress crashing on Linux > System limit for number of file watchers reached 'package.json' #6960
Comments
I'd suggest increasing the limit for the number of file watchers your system can watch https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details |
@jennifer-shehane True, I am going to do that. However, I'd suggest the expected behavior should be not to crash the entire process over this. |
Also, FYI, I have file watching explicitly disabled in
|
Hi, I think I meet the same problem that the options for disabling file watch do not work (it's happened at 7.7.0): https://github.com/berviantoleo/react-multi-crop/runs/3018043472?check_suite_focus=true Since my configuration like this: https://github.com/berviantoleo/react-multi-crop/blob/master/examples/demo/cypress.json But it's fine when at 7.6.0: https://github.com/berviantoleo/react-multi-crop/runs/2958413049?check_suite_focus=true |
Can we reopen this or do we create a separate issue for this? I am seeing in my project with this issue as well. |
I am running into this on 7.7.0. This is despite using |
It doesn't make sense to put it in the config file, because you do want it to watch for changes while writing/debugging tests. The correct way is to pass an override through the CLI: cypress run --config watchForFileChanges=false See: https://docs.cypress.io/guides/guides/command-line#cypress-run-config-lt-config-gt |
@adi518 , I agree with your approach but did this work for you though? it did not for me. Thanks. |
@jennifer-shehane, this is becoming a blocking issue for many devs out here, could it be prioritized higher in your teams list? it would be highly appreciated. A couple of thoughts:
Thanks, |
You are right, it doesn't work. I just tried it myself, since I have the same issue. Seems like the only workarounds now are to to modify the limit or downgrade Cypress to |
Thank you @Asharma86 for connecting the two issues, I apologize for not responding earlier. To everyone following this issue, given the number of open issues we have it it gets very hard to follow up on closed ones. When we are 100% sure the same use case with the same reproduction is actually failing then we will re-open the issue and follow up on it. If you have a blocking issue that is remotely linked, please open a new one. We can track duplicate issues, but we cannot track closed ones. Thank y'all in advance for understanding |
I ran into this recently and I would like to share how I fixed the issue. If you customize the webpack config then you should make sur to disable the watch feature of dev server. The watch feature is enabled by default in development mode. So I added an environment variable to tell if cypress is running on CI or not. In my case I also configured webpack to use polling. The config will depend on the version of webpack you are using. |
@Hunsu can you share your config? |
The chokidar dependency seems to be the problem. The fix that works for me is to set See also: cypress-io/github-action#317 (comment) |
Thanks @jorian-p . |
But using polling is inferior to fs events. |
So, I ran into this upgrading from 11.2 to 12.2. We're using GitLab, so I added this to the configuration, which disables watching when inside CI:
|
Works for me on Ubuntu + cypress/included:13.6.6 Thanks |
Hi, daily user of Cypress here.
Just found this corner case where Cypress.js is crashing.
Steps to reproduce
Not exactly sure but overall this is the scenario.
package.json
changes. In my case: two WebStorm windows & react build toolsCypress process output
System
Ubuntu 19.10
Cypress 4.3.0
node.js v12.16.1
Thanks! I love cypress. Let me know if I can provide more info.
The text was updated successfully, but these errors were encountered: