Cypress verify command failing #6184
Comments
|
We are experiencing the same error. We had a docker container working yesterday, rebuild the docker today, so newer versions installed through apt and now it's broken with the same error described above. |
|
I've got a docker image before it was broken. If I run the following command you can see cypress starts and correctly waits for something that's not running. and the I run the previous command again I get this output A workaround found by @krishofmans is running your command prefixed with |
|
We are seeing this as well, but our detailed error description isn't the same as the one listed above. Ours is: Due to this, the workaround listed above doesn't appear to work. I wouldn't normally assume they're the same issue, but they seem to have appeared along the same timeline. |
|
I logged this as well but thought it was resolved yesterday so I closed my issue. We're still seeing this and this issue has output with debug logging turned on: #6182 |
|
We are facing the same issue - we assume that the error is caused by one of these packages: All of them are also in the list of @GertVil. As quickfix we switched back to an older base image. |
|
We got this issue since yesterday after our container has been rebuilt. I couldn't figure out which package causes this problem. We are using the same packages which are implemented in the cypress/base:10 dockerfile. |
|
Got the source of the problem, Xvfb is run without Received signal 11 SEGV_MAPERR ffffef7352286c69
#0 0x56379509d3d9 (/root/.cache/Cypress/3.8.2/Cypress/Cypress+0x35d13d8)
r8: 0000000000000000 r9: 00007ffe15194500 r10: 00007ffe15194458 r11: 000000000000000e
r12: 00007ffe151945ac r13: 00007f595336d720 r14: ffffef7352286c39 r15: 00007f5954966200
di: 0000000000000000 si: 0000000000000020 bp: 0000000000000000 bx: 0000108e1c720e70
dx: 0000000000000001 ax: 0000000000000030 cx: 0000000000000001 sp: 00007ffe15194580
ip: 00007f595494a2dd efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000005
trp: 000000000000000e msk: 0000000000000000 cr2: ffffef7352286c69
[end of stack trace]
Calling _exit(1). Core file will not be generated.If is set fallback |
cypress-bot
bot
added
stage: work in progress
stage: needs review
|
I also hit the same issue since yesterday. The instance is started on a clean docker container with all the necessary package mentioned in the cypress.io website. I worked around this by pre-pending the commands with
So all in all it looks like a bug in Cypress, certainly related to #4624 . |
|
I'm seeing the same issue with a bionic docker image. We pinpointed it to the following packages: Wrapping our invocation of cypress with |
cypress-bot
bot
added
stage: pending release
and removed
stage: needs review
|
The code for this is done in cypress-io/cypress#6199, but has yet to be released. |
|
Added testing cypress-io/cypress-test-ci-environments#27 |
Temporary workaroundStart Xvfb yourself before running Cypress Xvfb :1 -screen 0 1280x800x24 &
export DISPLAY=:1
npx cypress verify
npx cypress run |
|
Alternatively, you can use xvfb-run to wrap the commands: |
|
Interesting, Ubuntu19 image works just fine cypress-io/cypress-docker-images#213 |
|
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior:
After an apt update of ubuntu 18.04 (yesterday 16/01/2020), the following cypress command return an error.
npx cypress verify/root/.cache/Cypress/3.8.2/Cypress/Cypress --no-sandbox --smoke-test --ping=24Desired behavior:
cypress verify should pass
Test code to reproduce
Versions
Ubuntu Linux - 18.04
Cypress Version: 3.8.2
Packages Versions :
apt-get install libgtk2.0-0 libgtk-3-0 libnotify-dev libgconf-2-4 libnss3 libxss1 libasound2 libxtst6 xauth xvfbThe text was updated successfully, but these errors were encountered: