"Cypress verify" fails within kubernetes #27209
Comments
|
Have you checked that the dependencies for Debian are installed according to the error message pointing to the documentation https://docs.cypress.io/guides/continuous-integration/introduction#Dependencies apt-get install libgtk2.0-0 libgtk-3-0 libgbm-dev libnotify-dev libgconf-2-4 libnss3 libxss1 libasound2 libxtst6 xauth xvfb |
|
Thanks for your fast feedback again @MikeMcC399 ! I had checked the dependencies with ldd: And doing the same with Funnily enough now tested with What I don't get though is that I just tested this with the docker image cypress/included:12.13.0 and from what I got was that the advantage of using the official cypress docker images were making sure of including all required dependencies and hence I am a bit suprised about the output. |
|
I repeated the same procedure but doing It just randomly fails sometimes and sometimes it don't |
You'll need to wait now for the Cypress team to pick your issue up via their triage process. |
|
Lots of info here - great debugging. I haven't run Cypress in k8s before, but I'll try now and see if I can reproduce. One thing sticks out to me - you mentioned 9.5.1 is working fine, but nothing beyond. Here's the diff for those two tags: I'll take a look and see if anything jumps out. |
|
I don't see anything obvious there causing issues - can you double check that it's definitely an issue between 9.5.1 and 9.5.2? If it really is, that vastly simplifies the debugging - we can just build a binary for each commit and figure it out that way. |
|
Tested again both versions, this is the debug output for Doing the same for 9.5.1 cypress verify succeeds 10 out of 10. I know this is not a 100% confirmation that there is no error in that version but it sure seems a lot different: I also had a short look at the comparison that you linked and also don't see anything that looks directly suspicious. Could the docker file creation be the one to look at here? Would be suprised if some major changes would have happened there for a minor version change of cypress itself but will try to compare them. |
|
The Debian version has a major version bump from
To see if the Debian version is related to the issue, perhaps install |
|
Yes, also stumbled across this. Will give that a try, was thinking about building my own custom image with buster instead of bullseye-slim but your approach is probably a lot easier. Will also try to test it on a different cluster. The one I am currently using is a little bit outdated, so that might be related. I will clarify which versions the different clusters have. |
|
@MikeMcC399 your proposal worked like a charm, used Will check now on the other cluster to see whether that's the reason. If so will create my own custom image with buster for the meantime until the cluster is upgrade. Will keep you posted. |
|
@luischre What components / versions would be changed by a potential cluster upgrade? |
|
Our pipeline is now running with a custom docker image including debian buster. Obviously it's not a long-term solution but for now it needs to suffice. With regards to components/version that might be changed. Next step that will be taken is upgrading the kubernetes version this is already planned, unfortunately I don't know the exact versions. Anyway I will retest once this is done to see whether that already fixes the problem. I had also done one test on another cluster with a slightly newer kubernetes version, there it worked without problems but besides the difference between kubernetes versions, there are more differences such as one is AWS based, the other one with Centos... I will close this issue as this seems to be an infratstructure issue on our side but will update it, once I retest the images, just in case it might help other people that run into the same issues. |
|
We had simmilar issue with SIGSEGV/SIGKILL in older image versions and SIGTRAP with newer image versions from IPC with docker in GL/CI. Maybe it is related with dbus permission or service with electron socket communication, but it needs more explore. So this workarround (install latest Cypress version based on cypress/included 9.5.1 docker image) works well. Thank you very much, helps a lot! |
|
Just a short update from my side. Update of the kubernetes version did not solve the issue, it's still persisting. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behavior
I am currently trying to migrate our cypress pipeline from version 9.2.1 to 12.13.0. We deploy 10 cypress pods within kubernetes that execute our tests in parallel.
For version 9.2.1 we created a custom cypress docker image based on the included image we only needed to adjust the browsers and hence had to customize it a bit.
For version 12.13.0 I used the cypress/factory image with the following arguments:
Our pods are started within a jenkins pipeline with the following pod yaml:
With version 9.2.1 we had the pipeline running without problems, with 12.13.0 however I can't get it to work properly. Some pods already encounter issue at the first start up of cypress with:
Others start up fine but then later during test execution when picking up a new test suite encounter the same issue.
I took the following steps so far to narrow down the error:
cypress/verify--> same errorThe weird thing is that cypress verify does not always fail within those pods. The first execution most likely will fail with one of those errors, afterwards it will sometimes succeed and sometimes it will fail.
From the versions I tested it seems that after version 9.5.1 our setup breaks somehow but I can't explain why.
I found a couple of similar issues within github and tested whatever solutions were given but nothing has worked for me so far:
I am running out of ideas why after 9.5.1 it no longer works with our setup, if anyone spots anything within the setup, any help would be greatly appreciated.
Desired behavior
Cypress verify should execute successfully within a kubernetes pod.
Test code to reproduce
See above pod configuration which is used within a jenkins pipeline
Cypress Version
12.13.0
Node version
18.16.0
Operating System
Linux 3.10 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
Debug Logs
No response
Other
No response
The text was updated successfully, but these errors were encountered: