Skip to content
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

file watch is not reliable on linux #1058

Closed
acthp opened this issue Dec 12, 2017 · 4 comments
Closed

file watch is not reliable on linux #1058

acthp opened this issue Dec 12, 2017 · 4 comments

Comments

@acthp
Copy link

acthp commented Dec 12, 2017

  • Operating System: ubuntu 14.04
  • Cypress Version: 1.1.4
  • Browser Version: chrome 60

Is this a Feature or Bug?

bug

Current behavior:

UI stops responding to file updates

Desired behavior:

UI consistently responds to file updates

How to reproduce:

Unclear. It happens very regularly, like every 5 minutes or so, during regular use. I sometimes convince myself that it happens after an error, like a syntax error in the spec file, but I've never been able to invoke the bug by introducing errors.

Once this state occurs, it can only be cleared by killing the cypress process and restarting. Hitting 'stop' on the UI, and restarting the spec file doesn't help. Neither does reloading the browser tab. It will never pick up changes to the spec file until the cypress process is killed and restarted.

Also, to be clear, this never happens on OSX.

@jennifer-shehane
Copy link
Member

@acthp This sounds very similar to this issue we found in v1.1.3 and was thought to be fixed in v1.1.4, could you try the steps from this issue and see if this reproduces the 'stop watching' behavior? Maybe there is something we missed in linux specifically with the bug fix.

Previous Issue: #1018

@jennifer-shehane jennifer-shehane added the stage: needs information Not enough info to reproduce the issue label Dec 12, 2017
@kuceb
Copy link
Contributor

kuceb commented Feb 16, 2018

You may want to check out this thread, because linux can run into problems with the inotify limit of the kernel: https://unix.stackexchange.com/questions/13751/kernel-inotify-watch-limit-reached

@jennifer-shehane
Copy link
Member

@acthp Any update on this from your end?

@jennifer-shehane
Copy link
Member

Closing as stale. No response in over a year. Please comment if you are still experiencing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants