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

Cypress not running after installing on windows 32bit #787

Closed
fr-ser opened this issue Oct 22, 2017 · 23 comments

Comments

@fr-ser
Copy link

commented Oct 22, 2017

Bug:

After the installation through npm I tried to open cypress. It fails with the following error message:

Stack trace:

C:\Users\froeh\Development\werkstatt-app>node node_modules//cypress/bin/cypress open
It looks like this is your first time using Cypress: 1.0.2

 ×  Verifying Cypress can run C:\Users\froeh\Development\werkstatt-app\node_modules\cypress\dist\Cypress
   → spawn UNKNOWN
An unexpected error occurred while verifying the Cypress executable.

Please search Cypress documentation for possible solutions:

https://on.cypress.io

Check if there is a GitHub issue describing this crash:

https://github.com/cypress-io/cypress/issues

Consider opening a new issue.
----------

Error: spawn UNKNOWN
at _errnoException (util.js:1019:11)
at ChildProcess.spawn (internal/child_process.js:325:11)
at Object.exports.spawn (child_process.js:494:9)
at C:\Users\froeh\Development\werkstatt-app\node_modules\cypress\lib\tasks\verify.js:82:22
at Promise._execute (C:\Users\froeh\Development\werkstatt-app\node_modules\bluebird\js\release\debuggability.js:300:9)
at Promise._resolveFromExecutor (C:\Users\froeh\Development\werkstatt-app\node_modules\bluebird\js\release\promise.js:483:18)
at new Promise (C:\Users\froeh\Development\werkstatt-app\node_modules\bluebird\js\release\promise.js:79:10)
at spawn (C:\Users\froeh\Development\werkstatt-app\node_modules\cypress\lib\tasks\verify.js:77:12)
at runSmokeTest (C:\Users\froeh\Development\werkstatt-app\node_modules\cypress\lib\tasks\verify.js:124:12)
at C:\Users\froeh\Development\werkstatt-app\node_modules\cypress\lib\tasks\verify.js:150:29
at tryCatcher (C:\Users\froeh\Development\werkstatt-app\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\Users\froeh\Development\werkstatt-app\node_modules\bluebird\js\release\promise.js:512:31)
at Promise._settlePromise (C:\Users\froeh\Development\werkstatt-app\node_modules\bluebird\js\release\promise.js:569:18)
at Promise._settlePromise0 (C:\Users\froeh\Development\werkstatt-app\node_modules\bluebird\js\release\promise.js:614:10)

at Promise._settlePromises (C:\Users\froeh\Development\werkstatt-app\node_modules\bluebird\js\release\promise.js:693:18)

at Promise._fulfill (C:\Users\froeh\Development\werkstatt-app\node_modules\bluebird\js\release\promise.js:638:18)
----------

Platform: win32 (10.0.10586)
Cypress Version: 1.0.2
  • Operating System: Windows 10 - 32 Bit
  • Cypress Version: 1.0.2
  • Browser Version: N/A
@bahmutov

This comment has been minimized.

Copy link
Collaborator

commented Oct 24, 2017

Hmm, we must print the exact command we are using when verifying successful install. Maybe binary was not installed or unzipped correctly due to proxy restrictions.

@MarcLoupias

This comment has been minimized.

Copy link

commented Oct 24, 2017

When a proxy deny your download request it is very clear :

...
> node index.js --exec install

Installing Cypress (version: 1.0.2)

 ×  Downloading Cypress    
   → Cypress Version: 1.0.2
    Unzipping Cypress      
    Finishing Installation 
The Cypress App could not be downloaded.

Please check network connectivity and try again:
----------

URL: https://download.cypress.io/desktop/1.0.2?platform=win32&arch=x64
Error: getaddrinfo ENOTFOUND download.cypress.io download.cypress.io:443
----------

Platform: win32 (6.1.7601)
Cypress Version: 1.0.2
@fr-ser

This comment has been minimized.

Copy link
Author

commented Oct 28, 2017

I also just did a reinstall of Cypress and do not get any error message during the installation (I still get the abovementioned error however)


> cypress@1.0.2 postinstall C:\Users\froeh\Development\werkstatt-app\node_modules\cypress
> node index.js --exec install

Installing Cypress (version: 1.0.2)

 V  Downloaded Cypress
 V  Unzipped Cypress
 V  Finished Installation C:\Users\froeh\Development\werkstatt-app\node_modules\cypress\dist\Cypress

You can now open Cypress by running: node_modules\.bin\cypress open

https://on.cypress.io/installing-cypress
+ cypress@1.0.2
added 67 packages in 450.01s`
@webia1

This comment has been minimized.

Copy link

commented Feb 6, 2018

same here

Installing Cypress (version: 1.4.2)

 ×  Downloading Cypress
   → Cypress Version: 1.4.2
    Unzipping Cypress
    Finishing Installation
The Cypress App could not be downloaded.

Please check network connectivity and try again:
----------

URL: https://download.cypress.io/desktop/1.4.2?platform=win32&arch=x64
Error: getaddrinfo ENOTFOUND download.cypress.io download.cypress.io:443
----------

Platform: win32 (10.0.15063)
Cypress Version: 1.4.2

We are behind a corporate proxy, that could be the reason.

@ANGDevAI

This comment has been minimized.

Copy link

commented Feb 15, 2018

Similar issue
Can somebody help me fixing the proxy/connectivity issue.

cypress@1.4.2 postinstall C:\Users\TT\Development\fxc-client\node_modules\cypress
node index.js --exec install

Installing Cypress (version: 1.4.2)

 ×  Downloading Cypress
   → Cypress Version: 1.4.2
    Unzipping Cypress
    Finishing Installation
The Cypress App could not be downloaded.

Please check network connectivity and try again:
----------

URL: https://download.cypress.io/desktop/1.4.2?platform=win32&arch=x64
Error: connect ECONNREFUSED 104.25.215.23:443
----------

Platform: win32 (6.1.7601)
Cypress Version: 1.4.2
npm verb lifecycle cypress@1.4.2~postinstall: unsafe-perm in lifecycle true
npm verb lifecycle cypress@1.4.2~postinstall: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users\TT\Development\fxc-client\node_modules\cypress\node_modules\.bin;C:\Users\TT\Development\fxc-client\node_modul
s\.bin;C:\WINDOWS\system32\WindowsPowerShell\v1.0\;C:\Python27\;C:\Python27\Scripts;C:\ProgramData\Oracle\Java\javapath
C:\Program Files\Java\jdk1.8.0_60\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\Windo
sPowerShell\v1.0\;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseSVN\bin;C:\apache-maven-3.3.3\bi
;C:\Users\K\AppData\Roaming\npm;C:\Program Files (x86)\Git\cmd;C:\Users\TT\AppData\Local\Programs\Git\cmd;C:\
rogram Files\nodejs\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\WINDOWS\System32\WindowsPo
erShell\v1.0\;C:\Program Files\Microsoft Application Virtualization\Client ;C:\Ruby23\bin;C:\Users\TT\AppData\Roam
ng\npm;C:\Users\TT\AppData\Local\Programs\Fiddler

npm verb If you need help, you may report this error at:
npm verb     <https://github.com/npm/npm/issues>
npm WARN Error: EPERM: operation not permitted, rmdir 'C:\Users\TT\Development\fxc-client\node_modules\@types'
npm WARN  { Error: EPERM: operation not permitted, rmdir 'C:\Users\TT\Development\fxc-client\node_modules\@types'
npm WARN   errno: -4048,
npm WARN   code: 'EPERM',
npm WARN   syscall: 'rmdir',
npm WARN   path: 'C:\\Users\\TT\\Development\\fxc-client\\node_modules\\@types' }
npm verb
npm verb Please try running this command again as root/Administrator.
npm verb stack Error: cypress@1.4.2 postinstall: `node index.js --exec install`
npm verb stack Exit status 1
npm verb stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:279:16)
npm verb stack     at emitTwo (events.js:106:13)
npm verb stack     at EventEmitter.emit (events.js:194:7)
npm verb stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
npm verb stack     at emitTwo (events.js:106:13)
npm verb stack     at ChildProcess.emit (events.js:194:7)
npm verb stack     at maybeClose (internal/child_process.js:899:16)
npm verb stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
npm verb pkgid cypress@1.4.2
npm verb cwd C:\Users\TT\Development\fxc-client
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "ins
tall" "cypress" "--verbose"
npm ERR! node v7.7.1
npm ERR! npm  v4.1.2
npm ERR! code ELIFECYCLE

npm ERR! cypress@1.4.2 postinstall: `node index.js --exec install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the cypress@1.4.2 postinstall script 'node index.js --exec install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the cypress package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node index.js --exec install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs cypress
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls cypress
npm ERR! There is likely additional logging output above.
npm verb exit [ 1, true ]

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\TT\Development\fxc-client\npm-debug.log
@fr-ser

This comment has been minimized.

Copy link
Author

commented Feb 15, 2018

I do believe that the issue I have in the original post is different than the ones you mention here.
I get no error message downloading, but only on the first run.

@NAPOLEON039

This comment has been minimized.

Copy link

commented Feb 23, 2018

I get this same error when I try to run cypress :(

@kutlaykural

This comment has been minimized.

Copy link

commented Apr 9, 2018

Hi all,
My system is windows 7 x86
I downloaded cypress last update from;
https://download.cypress.io/desktop?platform=win32&arch=x86
but it says "this program is incompetible with your Windows. Please check program requirements whether x86 or x64"
what can I do?

@davegahn

This comment has been minimized.

Copy link

commented Apr 10, 2018

Same errors. Has anybody solved this?..

@itaditya

This comment has been minimized.

Copy link

commented Jun 1, 2018

I'm having the same issue as mentioned in title

$ $(npm bin)/cypress open

It looks like this is your first time using Cypress: 3.0.1

 x  Verifying Cypress can run C:\Users\dev_adi\AppData\Local\Cypress\Cache\3.0.1\Cypress
   → spawn UNKNOWN
An unexpected error occurred while verifying the Cypress executable.

Please search Cypress documentation for possible solutions:

https://on.cypress.io

Check if there is a GitHub issue describing this crash:

https://github.com/cypress-io/cypress/issues

Consider opening a new issue.
----------

Error: spawn UNKNOWN
at _errnoException (util.js:999:13)
at ChildProcess.spawn (internal/child_process.js:340:11)
at Object.exports.spawn (child_process.js:499:9)
at F:\git\Testing\cypress-handson\node_modules\cypress\lib\tasks\verify.js:67:22
at Promise._execute (F:\git\Testing\cypress-handson\node_modules\bluebird\js\release\debuggability.js:300:9)
at Promise._resolveFromExecutor (F:\git\Testing\cypress-handson\node_modules\bluebird\js\release\promise.js:483:18)
at new Promise (F:\git\Testing\cypress-handson\node_modules\bluebird\js\release\promise.js:79:10)
at spawn (F:\git\Testing\cypress-handson\node_modules\cypress\lib\tasks\verify.js:62:12)
at runSmokeTest (F:\git\Testing\cypress-handson\node_modules\cypress\lib\tasks\verify.js:109:12)
at F:\git\Testing\cypress-handson\node_modules\cypress\lib\tasks\verify.js:132:29
at tryCatcher (F:\git\Testing\cypress-handson\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (F:\git\Testing\cypress-handson\node_modules\bluebird\js\release\promise.js:512:31)
at Promise._settlePromise (F:\git\Testing\cypress-handson\node_modules\bluebird\js\release\promise.js:569:18)
at Promise._settlePromise0 (F:\git\Testing\cypress-handson\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (F:\git\Testing\cypress-handson\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (F:\git\Testing\cypress-handson\node_modules\bluebird\js\release\promise.js:638:18)
----------

Platform: win32 (6.1.7601)
Cypress Version: 3.0.1
@brian-mann

This comment has been minimized.

Copy link
Member

commented Jun 1, 2018

@itaditya we've never seen this before. Perhaps it is a permissions issue. It looks like you're trying to run Cypress across a network drive - since I see it's installed to C:/ but your node modules is in F:/

Can you run Cypress in debug mode so we get all of the logs output?

set DEBUG=cypress:cli
npm install

You can also try...

set DEBUG=cypress:cli 
npx cypress verify
@Davidcreador

This comment has been minimized.

Copy link

commented Jun 26, 2018

> node index.js --exec install

  cypress:cli installing Cypress from NPM +0ms
  cypress:cli installing with options {} +0ms
  cypress:cli version in package.json is 3.0.1 +17ms
  cypress:cli no binary installed under cli version +285ms
  cypress:cli checking local file C:\Users\DPastor\Desktop\Dev\party-landing-web\3.0.1 cwd C:\Users\DPastor\Desktop\Dev\party-landing-web\node_modules\cypress +153ms
  cypress:cli preparing to download and unzip version  3.0.1 to path C:\Users\DPastor\AppData\Local\Cypress\Cache\3.0.1 +57ms
Installing Cypress (version: 3.0.1)

  cypress:cli needed Cypress version: 3.0.1 +0ms
  cypress:cli downloading cypress.zip to "C:\Users\DPastor\AppData\Local\Temp\cypress.zip" +69ms
 \  Downloading Cypress
    Unzipping Cypress
 |  Downloading Cypress
    Unzipping Cypress
 ×  Downloading Cypress
   → Cypress Version: 3.0.1
    Unzipping Cypress
    Finishing Installation
The Cypress App could not be downloaded.

Please check network connectivity and try again:
----------

URL: https://download.cypress.io/desktop/3.0.1?platform=win32&arch=x64
Error: unable to get local issuer certificate
----------

Platform: win32 (10.0.15063)
Cypress Version: 3.0.1

I am getting the same error, I just set it to DEBUG and that is what I am getting. Please review it and let me know what is happening and what could be the possible solution for it? I am on windows btw.

@AlxndrMlk

This comment has been minimized.

Copy link

commented Aug 19, 2018

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'test' ]
2 info using npm@6.2.0
3 info using node@v10.9.0
4 verbose run-script [ 'pretest', 'test', 'posttest' ]
5 info lifecycle warsawjs-workshop-23-shopping-cart@0.1.0~pretest: warsawjs-workshop-23-shopping-cart@0.1.0
6 info lifecycle warsawjs-workshop-23-shopping-cart@0.1.0~test: warsawjs-workshop-23-shopping-cart@0.1.0
7 verbose lifecycle warsawjs-workshop-23-shopping-cart@0.1.0~test: unsafe-perm in lifecycle true
8 verbose lifecycle warsawjs-workshop-23-shopping-cart@0.1.0~test: PATH: C:\Users\Ol\AppData\Roaming\nvm\v10.9.0\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\Ol\Documents\PROGRAMMING\WAW_JS_2\warsawjs-workshop-23-shopping-cart\node_modules\.bin;C:\Users\Ol\bin;C:\Program Files\Git\mingw32\bin;C:\Program Files\Git\usr\local\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\mingw32\bin;C:\Program Files\Git\usr\bin;C:\Users\Ol\bin;C:\Program Files\Common Files\Oracle\Java\javapath;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Intel\TXE Components\TCS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files\Hewlett-Packard\SimplePass;C:\Program Files\Intel\TXE Components\DAL;C:\Program Files\Intel\TXE Components\IPT;C:\Program Files\MATLAB\MATLAB Compiler Runtime\v710\runtime\win32;C:\ProgramData\Anaconda3;C:\ProgramData\Anaconda3\Scripts;C:\ProgramData\Anaconda3\Library\bin;C:\MinGW\bin;C:\Program Files\Git\cmd;C:\Program Files\Skype\Phone;C:\Program Files\wkhtmltopdf\bin;%NVM_HOME%;%NVM_SYMLINK%;C:\Users\Ol\AppData\Local\Microsoft\WindowsApps;C:\Users\Ol\AppData\Local\atom\bin;C:\Users\Ol\AppData\Local\Microsoft\WindowsApps;C:\Users\Ol\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Program Files\Git\usr\bin\vendor_perl;C:\Program Files\Git\usr\bin\core_perl
9 verbose lifecycle warsawjs-workshop-23-shopping-cart@0.1.0~test: CWD: C:\Users\Ol\Documents\PROGRAMMING\WAW_JS_2\warsawjs-workshop-23-shopping-cart
10 silly lifecycle warsawjs-workshop-23-shopping-cart@0.1.0~test: Args: [ '/d /s /c', 'cypress open' ]
11 silly lifecycle warsawjs-workshop-23-shopping-cart@0.1.0~test: Returned: code: 1  signal: null
12 info lifecycle warsawjs-workshop-23-shopping-cart@0.1.0~test: Failed to exec test script
13 verbose stack Error: warsawjs-workshop-23-shopping-cart@0.1.0 test: `cypress open`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Users\Ol\AppData\Roaming\nvm\v10.9.0\node_modules\npm\node_modules\npm-lifecycle\index.js:304:16)
13 verbose stack     at EventEmitter.emit (events.js:182:13)
13 verbose stack     at ChildProcess.<anonymous> (C:\Users\Ol\AppData\Roaming\nvm\v10.9.0\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:182:13)
13 verbose stack     at maybeClose (internal/child_process.js:961:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:250:5)
14 verbose pkgid warsawjs-workshop-23-shopping-cart@0.1.0
15 verbose cwd C:\Users\Ol\Documents\PROGRAMMING\WAW_JS_2\warsawjs-workshop-23-shopping-cart
16 verbose Windows_NT 10.0.16299
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "test"
18 verbose node v10.9.0
19 verbose npm  v6.2.0
20 error code ELIFECYCLE
21 error errno 1
22 error warsawjs-workshop-23-shopping-cart@0.1.0 test: `cypress open`
22 error Exit status 1
23 error Failed at the warsawjs-workshop-23-shopping-cart@0.1.0 test script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

On Win 10 32bit I get the above log. cypress itself opens and returns options screen, but returns the above output when cypress open executed.

Will be grateful for feedback. Thanks!

@flotwig flotwig referenced this issue Feb 20, 2019

Merged

Improved proxy support #3531

38 of 38 tasks complete

@jennifer-shehane jennifer-shehane changed the title Cypress not running after installing on windows Cypress not running after installing on windows 32bit Mar 6, 2019

@jennifer-shehane

This comment has been minimized.

Copy link
Member

commented Mar 6, 2019

Where are you running the cypress open/cypress run command from? Is it in a plain terminal (cmd) window or from a terminal within your IDE program? I've read that running from the IDE terminal may cause this issue.

@Saibamen

This comment has been minimized.

Copy link
Contributor

commented Mar 6, 2019

  1. Does installing latest npm and node helps you?
  2. Your npm and node is in global variables? (type npm --version and node --version to test it)
  3. Please try install Cypress with admin - right click on cmd.exe and click "Run as Administrator"
  4. Can you download Cypress directly from your browser: http://download.cypress.io/desktop or https://download.cypress.io/desktop/3.1.5?platform=win32&arch=x64
@Saibamen

This comment has been minimized.

Copy link
Contributor

commented Mar 6, 2019

@AlxndrMlk Please try open it by adding

"scripts": {
    "cypress": "cypress"
  },

into your package.json file and run it by executing npm run cypress open

@PiyushTalwalkar

This comment has been minimized.

Copy link

commented Mar 14, 2019

Can I get some help on above issue

@fr-ser

This comment has been minimized.

Copy link
Author

commented Mar 14, 2019

Just a quick heads up. I don't even use Windows anymore and cannot give any input here. Maybe the other posters have the same issue and can help....

@timelights

This comment has been minimized.

Copy link

commented Mar 14, 2019

@brian-mann

This comment has been minimized.

Copy link
Member

commented Apr 1, 2019

@flotwig or @jennifer-shehane is #3531 fixing the issue here? It says it's addressing the comments... should we lock this issue then?

@jennifer-shehane

This comment has been minimized.

Copy link
Member

commented Apr 1, 2019

@brian-mann Many of the earlier comments were experiencing a proxy issue that will be resolved by this PR #3531 and the release of 3.3.0 - specifically these comments:

Although the original issue is the error below specifically, and this should be left open for this.

 x  Verifying Cypress can run C:\Users\dev_adi\AppData\Local\Cypress\Cache\3.0.1\Cypress
   → spawn UNKNOWN

Although, I think this other PR may give more insight into why the spawn UNKNOWN error is occuring since it specifically adds more login to cypress verify #3807

@flotwig

This comment has been minimized.

Copy link
Member

commented Apr 8, 2019

We have fixed this by also building for Windows 32-bit.

The code for this is done in cypress-io/cypress#3877, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

@cypress-bot

This comment has been minimized.

Copy link

commented May 17, 2019

Released in 3.3.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.