Cypress was killed with SIGTERM (Termination) #22440
Unanswered
davidjeyachandran
asked this question in
Questions and Help
Replies: 2 comments 1 reply
-
What fixed it for me was that I installed Cypress 10.2.0 in a subdirectory, that wouldn't work for some reason, but when I installed Cypress in my username director it was able to run in my coding subdirectory. Let me know if that works! Edit: the install was done in terminal |
Beta Was this translation helpful? Give feedback.
1 reply
-
I used |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Cypress 10 has been working beautifully and it stopped working yesterday afternoon. It's not a bug with Cypress because I've tested the same repository on other machines. I think Cypress stopped abruptly and now I'm getting the following error:
I've tried:
I've also run cypress with the debug flag & I'm happy to post this but it didn't provide me any clues.
DEBUG=cypress:cli npx cypress open
I then tried installing different Cypress versions (10.2.0, 10.1.0, 10.03). I know it's not the version because 10.1 and 10.2 were working fine on my machine. I tried the same repository on another machine and just did an
npm install
andnpx cypress open
and it just worked.Any ideas? I think I've completely uninstalled Cypress and reinstalled it. Could SIGTERM keep a track of processes that have failed and immediately kills Cypress.
Beta Was this translation helpful? Give feedback.
All reactions