-
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 in docker crashing randomly with SIGTRAP #27564
Comments
Which CI are you using? I have seen SIGTRAP produced on That may not be related to your issue, however the error messages are similar to yours. It is also strange that you have apparently random problems. |
We are using Jenkins as CI system |
Thanks for filling in that information gap! Cypress 13.2.0 was released yesterday, together with new Docker images. This includes some updates which have improved gpu handling. You might like to try this new version to see if it improves your outcome. |
Hey, sorry for the long silence 😅 Ihave just tried the latest version (13.3.3) of cypress with the latest docker image (node-20.9.0-chrome-118.0.5993.88-1-ff-118.0.2-edge-118.0.2088.46-1) And it looks like we now moved from SIGTRAP to SIGSEGV (yay, progress 😄)
|
Did I understand you correctly that you are running the Cypress Docker container inside a Debian container on Ubuntu or did I misunderstand and the Cypress Docker container runs directly under Ubuntu? Edit: According to The Cypress Docker container |
I'm on @DGuentherTV's team. @MikeMcC399 Correct, the image is built on Debian and runs either on baremetal Ubuntu 22.04 machines (where it's a little better), or on Ubuntu 22.04 VMs (where it's real bad). The difference between running on baremetal or VMs is mostly an interesting curiosity, the problem appears on either. This is very frustrating for our entire organization because we run Cypress as part of every CI build, and devs need to wait 16 minutes for all Cypress tests to pass successfully only for it to exit with
We also don't know what our best bet would be for circumventing the issue, as we haven't found anything that even remotely improves the situation. Should we try a different Docker image, maybe one not built on Debian and/or roll one ourselves? Currently, debates are starting about switching to Playwright just to not have this problem :/ |
|
FYI: We have now created a docker image based on Might be the Debian update, might be some setting/env that we did not set in comparison to the official cypress images. |
Great news! I'd suggest that you close this issue now if you have a solution.
|
Current behavior
When running in our CI environment, Cypress (verify, info, run) randomly crashes with this error message:
The weird thing is, that this happens seemingly random and may work and fail in the same container
f.ex. verify works, but then run crashes
even running verify 2 times could work once or twice or not at all
Even weirder: we didn't change anything in the docker image nor did we update cypress, yet the problem got somehow worse
Running the cypress binary directly with an attached gdb results in the following backtrace when this crash happens:
We have tried a lot so far:
--disable-gpu
--ipc=host
,-e HOME=/root
cypress/browsers:node-18.16.0-chrome-114.0.5735.133-1-ff-114.0.2-edge-114.0.1823.51-1
Maybe someone here has an idea or knows where we can find help
Desired behavior
Cypress should verify and run reliably
Test code to reproduce
N/A
Cypress Version
12.17.3
Node version
18.17.0
Operating System
Host: Ubuntu 22.04, Container: Debian - 11.6
Debug Logs
No response
Other
No response
The text was updated successfully, but these errors were encountered: