-
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 hangs on Verifying Cypress can run #7158
Comments
This also happened to me once using 4.5.0.
|
For me, I never reach the "Command failed" stage. It simply hangs. What additional information can I provide? |
Same problem for me running WSL 2 on Windows 10. |
Sorry for the late response - Mestru's link fixed it for me. It was a GUI on WSL issue. Thanks Mestru. |
@jennifer-shehane Could we have this reopened? I couldn't solve it via that link and either way the command shouldn't hang. It would be great to have an explanation added to the docs about setting up cypress on WSL2. |
Solved it by updating my distro to WSL2. It would be great to mention somewhere in the docs the setup for WSL2. |
I created a new issue in our docs to document WSL2 setup here: cypress-io/cypress-documentation#3022. Our documentation is open source and contributions are welcome. |
It looks like this issue was hijacked by WSL2, but the original post was about WSL, not WSL2. Whenever I try to run System: Windows 10 (10.0.18363.1016) WSL Ubuntu 18.04.3 LTS
|
This issue is still present. Any ideas ? |
Getting it right now on WSL and Cypress 5.2 |
I haven't found any fix for WSL, I ended up installing nodejs and cypress via powershell. |
Anyone has a fix for this. I have the same problem concerning WSL 2. Can't run cypress and the cypress:open command simply hangs without throwing any result. |
I have the same issue with Cypress 4.12.1 after migrating from Jenkins 2.150.2 to 2.235.5 on Openshift with the same slave agent container, based on the following image:
Output on Jenkins 2.150.2:
And on Jenkins 2.235.5:
Only difference I see is the location where Cypress is ran from ( |
After adding Seems that anybody who's having a similar issue on Linux should be able to resolve it like this. |
Current behavior:
Installed Cypress through npm and running Cypress from command line for the first time, Cypress hangs on the Verifying Cypress can run step indefinitely:
Below is the output when running debug: DEBUG=cypress:* npm run cypress:open
Desired Behavior
Open Cypress
Test code to reproduce
npm install --save-dev cypress
"scripts": { "cypress:open": "cypress open" },
npm run cypress:open
Versions
Cypress 4.4.1
Windows 10 WSL Ubuntu 18.04 LTS
npm 6.14.4
The text was updated successfully, but these errors were encountered: