-
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 fails with SIGTRAP error in AzureDevops Linux #30635
Comments
Hi @aurelgerisch, you would want to make sure you have the required dependencies installed. If you believe everything is installed correctly, you can run with the CYPRESS_SKIP_VERIFY environment variable to skip the verify step. If it's any help, we also maintain docker images for testing with Cypress. Finally, you may want to check out the Cypress Discord Community to see if anyone else has encountered the same issue with AzureDevops. |
I have run it with the environment variable. The verify step was skipped, but the Cypress Run to execute the tests failed with the same error. I attached the detailed logs. What can cause this issue? In other environments and locally the cypress installation is fine and the tests are running.
|
I know that in the past, we've seen SIGTRAP errors in our own docker images if there are permission/user issues. Is it possible that you're running into that type of scenario? |
Current behavior
Cypress Tests should run in a Self Hosted Linux Machine on Azure Devops. When running Cypress after installing it the command verifiy fails. We get the following output.
Command was killed with SIGTRAP (Debugger breakpoint)
Platform:
linux-x64 (Ubuntu - 22.04)
Cypress Version: 13.15.2
Desired behavior
When Cypress Verify fails it should give a hint why it can not run. What could be a possible cause for the SIGTRAP error during the Cypress Smoke Test?
Test code to reproduce
npx cypress verify
Cypress Version
13.15.2
Node version
v18.20.4
Operating System
Ubuntu - 22.04
Debug Logs
Other
No response
The text was updated successfully, but these errors were encountered: