error running cypress open #859

uptownhr · 2017-10-31T01:58:47Z

On a fresh install of cypress through npm install cypress, and fresh install of Ubuntu, attempting to launch causes an error after the browser opens.

Another ticket - #842 - that was previously open mentioned that my tmp dir may be full. But,
https://ipfs.io/ipfs/QmZsZxNnBXA3Qpvx1z1Q1fgWfb9J5eQajVLkgfybsuwt2X

Filesystem                   Size  Used Avail Use% Mounted on
udev                         5.8G     0  5.8G   0% /dev
tmpfs                        1.2G   17M  1.2G   2% /run
/dev/mapper/ubuntu--vg-root  446G   15G  409G   4% /
tmpfs                        5.9G  665M  5.2G  12% /dev/shm
tmpfs                        5.0M  4.0K  5.0M   1% /run/lock
tmpfs                        5.9G     0  5.9G   0% /sys/fs/cgroup
/dev/sda2                    473M  125M  324M  28% /boot
/dev/sda1                    511M  3.4M  508M   1% /boot/efi
tmpfs                        1.2G   52K  1.2G   1% /run/user/1000

This is also a ls -lah of my /tmp dir

ls /tmp -lah
total 2.1M
drwxrwxrwt 50 root   root   4.0K Oct 30 19:03 .
drwxr-xr-x 24 root   root   4.0K Oct 30 14:41 ..
drwx------  2 uptown uptown 4.0K Oct 30 15:20 .com.google.Chrome.2oaeZL
drwx------  2 uptown uptown 4.0K Oct 30 16:55 .com.google.Chrome.sJB9e3
-rw-------  1 uptown uptown    0 Oct 30 15:19 config-err-H2fXYA
-rw-------  1 uptown uptown    0 Oct 30 16:41 config-err-K6WKua
drwxrwxr-x  2 uptown uptown 4.0K Oct 30 18:56 cypress

I have also tried changing my tmp directory just to be safe and the issue still occurs.

Operating System: Ubuntu
Cypress Version: 1.0.3
Browser Version: 62.0.3202.75

Is this a Feature or Bug?

Bug

Current behavior:

Fails to launch

Desired behavior:

Should launch and run tests

How to reproduce:

npm install cypress
node_modules/.bin/cypress open

Test code:

describe('My First Test', function() {
    it('Does not do much!', function() {
	expect(true).to.equal(false)
    })
})

Additional Info (images, stack traces, etc)

{ Error: watch /home/uptown/Bambee/dev/cyp/package.json ENOSPC
    at exports._errnoException (util.js:1026:11)
    at FSWatcher.start (fs.js:1439:19)
    at Object.fs.watch (fs.js:1466:11)
    at createFsWatchInstance (/home/uptown/Bambee/dev/cyp/node_modules/cypress/dist/Cypress/resources/app/packages/server/node_modules/chokidar/lib/nodefs-handler.js:37:15)
    at setFsWatchListener (/home/uptown/Bambee/dev/cyp/node_modules/cypress/dist/Cypress/resources/app/packages/server/node_modules/chokidar/lib/nodefs-handler.js:80:15)
    at FSWatcher.NodeFsHandler._watchWithNodeFs (/home/uptown/Bambee/dev/cyp/node_modules/cypress/dist/Cypress/resources/app/packages/server/node_modules/chokidar/lib/nodefs-handler.js:228:14)
    at FSWatcher.NodeFsHandler._handleFile (/home/uptown/Bambee/dev/cyp/node_modules/cypress/dist/Cypress/resources/app/packages/server/node_modules/chokidar/lib/nodefs-handler.js:255:21)
    at FSWatcher.<anonymous> (/home/uptown/Bambee/dev/cyp/node_modules/cypress/dist/Cypress/resources/app/packages/server/node_modules/chokidar/lib/nodefs-handler.js:473:21)
    at /home/uptown/Bambee/dev/cyp/node_modules/cypress/dist/Cypress/resources/app/packages/server/node_modules/graceful-fs/polyfills.js:287:18
    at FSReqWrap.oncomplete (fs.js:123:15)

  code: 'ENOSPC',
  errno: 'ENOSPC',
  syscall: 'watch /home/uptown/Bambee/dev/cyp/package.json',
  filename: '/home/uptown/Bambee/dev/cyp/package.json' }
Error: watch /home/uptown/Bambee/dev/cyp/package.json ENOSPC
    at exports._errnoException (util.js:1026:11)
    at FSWatcher.start (fs.js:1439:19)
    at Object.fs.watch (fs.js:1466:11)
    at createFsWatchInstance (/home/uptown/Bambee/dev/cyp/node_modules/cypress/dist/Cypress/resources/app/packages/server/node_modules/chokidar/lib/nodefs-handler.js:37:15)
    at setFsWatchListener (/home/uptown/Bambee/dev/cyp/node_modules/cypress/dist/Cypress/resources/app/packages/server/node_modules/chokidar/lib/nodefs-handler.js:80:15)
    at FSWatcher.NodeFsHandler._watchWithNodeFs (/home/uptown/Bambee/dev/cyp/node_modules/cypress/dist/Cypress/resources/app/packages/server/node_modules/chokidar/lib/nodefs-handler.js:228:14)
    at FSWatcher.NodeFsHandler._handleFile (/home/uptown/Bambee/dev/cyp/node_modules/cypress/dist/Cypress/resources/app/packages/server/node_modules/chokidar/lib/nodefs-handler.js:255:21)
    at FSWatcher.<anonymous> (/home/uptown/Bambee/dev/cyp/node_modules/cypress/dist/Cypress/resources/app/packages/server/node_modules/chokidar/lib/nodefs-handler.js:473:21)
    at /home/uptown/Bambee/dev/cyp/node_modules/cypress/dist/Cypress/resources/app/packages/server/node_modules/graceful-fs/polyfills.js:287:18
    at FSReqWrap.oncomplete (fs.js:123:15)

The text was updated successfully, but these errors were encountered:

bahmutov · 2017-10-31T02:07:28Z

We never had this error in our testing, but maybe you can try some solutions described here: https://stackoverflow.com/questions/22475849/node-js-error-enospc

brian-mann · 2017-10-31T14:58:06Z

Duplicate of #842

This is a problem on your end of things - I don't believe there's anything to do on Cypress' end. Would reopen if anyone can suggest if there's anything we could do to prevent this.

uptownhr · 2017-10-31T23:49:13Z

I'd recommend adding something into the documentation to aid in addressing and explaining the issue.

As of now, I've tried the solutions on 842 and still experiencing the problem. Unable to proceed with Cypress. As I mentioned, I'm a machine that is fresh install of Ubuntu 16.04. I'm using an lvm volume but other than that, I have done nothing from the standard install.

bahmutov · 2017-10-31T23:54:47Z

James is there a CI or Docker environment that is identical to yours we can test on? Just hard to believe that electron plus npm project would be impossible to run on stock ubuntu 16!

…

Sent from my iPhone

On Oct 31, 2017, at 19:49, James Lee ***@***.***> wrote: I'd recommend adding something into the documentation to aid in addressing and explaining the issue. As of now, I've tried the solutions on 842 and still experiencing the problem. Unable to proceed with Cypress. As I mentioned, I'm a machine that is fresh install of Ubuntu 16.04. I'm using an lvm volume but other than that, I have done nothing from the standard install. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

uptownhr · 2017-11-08T05:08:37Z

@bahmutov I have a feeling this is actually related to my environment. I'm using docker and volumizing my app dir. It contains node_modules and since cypress is installed as root inside the container, i think this is probably causing file perm issues when i run cypress outside the container.

I tried running on a completely new project and I'm not seeing this issue.

bahmutov · 2017-11-08T10:01:22Z

Great that might be it!

…

Sent from my iPhone

On Nov 8, 2017, at 06:08, James Lee ***@***.***> wrote: @bahmutov I have a feeling this is actually related to my environment. I'm using docker and volumizing my app dir. It contains node_modules and since cypress is installed as root inside the container, i think this is probably causing file perm issues when i run cypress outside the container. I tried running on a completely new project and I'm not seeing this issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

brentkirkland · 2017-11-14T21:40:27Z

Was getting this on a fresh Ubuntu 16.04 install.

Running the following helps:

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

suulola · 2019-12-06T10:57:51Z

i also had this same issue on ubuntu 18.04 when i ran the
./cypress open
from node_modules/.bin folder

Suprisingly, it worked when i backed up to the parent directory and ran
./node_modules/.bin/cypress open

brian-mann closed this as completed Oct 31, 2017

jennifer-shehane added the OS: linux label Nov 1, 2017

bahmutov mentioned this issue Nov 2, 2017

Make base image for Ubuntu 16 cypress-io/cypress-docker-images#19

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

error running cypress open #859

error running cypress open #859

uptownhr commented Oct 31, 2017 •

edited

bahmutov commented Oct 31, 2017

brian-mann commented Oct 31, 2017

uptownhr commented Oct 31, 2017

bahmutov commented Oct 31, 2017 via email

uptownhr commented Nov 8, 2017

bahmutov commented Nov 8, 2017 via email

brentkirkland commented Nov 14, 2017

suulola commented Dec 6, 2019

error running cypress open #859

error running cypress open #859

Comments

uptownhr commented Oct 31, 2017 • edited

Is this a Feature or Bug?

Current behavior:

Desired behavior:

How to reproduce:

Test code:

Additional Info (images, stack traces, etc)

bahmutov commented Oct 31, 2017

brian-mann commented Oct 31, 2017

uptownhr commented Oct 31, 2017

bahmutov commented Oct 31, 2017 via email

uptownhr commented Nov 8, 2017

bahmutov commented Nov 8, 2017 via email

brentkirkland commented Nov 14, 2017

suulola commented Dec 6, 2019

uptownhr commented Oct 31, 2017 •

edited