Menu
I am stuck in this problem. I am running cypress tests. When I run locally, it runs smoothly. when I run in circleCI, it throws error after some execution.
Here is what i am getting:
[334:1020/170552.614728:ERROR:bus.cc(392)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[334:1020/170552.616006:ERROR:bus.cc(392)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[334:1020/170552.616185:ERROR:bus.cc(392)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[521:1020/170552.652819:ERROR:gpu_init.cc(441)] Passthrough is not supported, GL is swiftshader
Current behavior:
When I run my specs headless on the circleCI, Cypress closed unexpectedly with a socket error.
Error code:
The Test Runner unexpectedly exited via a exit event with signal SIGSEGV
Please search Cypress documentation for possible solutions:
https://on.cypress.io
Platform: linux (Debian - 10.5)
Cypress Version: 8.6.0
759
asked Oct 21 '21 08:10
Are people still experiencing this in the current version of Cypress? Yes. I'm seeing this issue on GitLab 13.9.3 with GitLab Runner 13.9.0 with Cypress 6.8.0 with cypress/base:14.6.0.
I found that an easy way to trigger this (getting either SIGABRT or SIGILL) is to try to run multiple cypress run processes at once, in the same directory. I've tried to isolate them by setting independent values for screenshotsFolder, videosFolder, etc. but it seems like some kind of state is still shared.
Downgrading Cypress or any dependency is bad practice. There is likely deprecated or buggy code in either your Cypress tests or your dependencies which causes the shutdown. I had this same issue on within our Azure builds as well. We only recently migrated from Cypress 8.4.0. Going back to that has solved the problem.
Surprisingly it does not happen in CI (probably not Linux either). Renovate seamslessly updates, passes CI, we pull and SIGABIRT. Edit: I dare say this needs a combinatorial test config.
Issue resolved by reverting back cypress version to 7.6.0.
109
answered Oct 16 '22 23:10
I had this same issue on within our Azure builds as well. We only recently migrated from Cypress 8.4.0. Going back to that has solved the problem.
1
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
