cypress: "Failed to connect to the bus: Address does not contain a colon" throws a SIGSEGV error

UPDATE [by Cypress Team]: Please see https://github.com/cypress-io/cypress/issues/19299#issuecomment-1090474752 for details. `Failed to connect to the bus` is a harmless message and will be silenced in future Cypress releases.

In addition, see https://github.com/cypress-io/cypress/issues/19299#issuecomment-1092084463 for some discussion of potential solutions to SIGSEGV.

Current behavior

Our tests intermittently crash in our Docker runs with the error below. We get the Failed to connect to the bus: Address does not contain a colon error often, but it doesn’t crash it.

But, when it does crash, that error is always the last one before the SIGSEGV.

I think we’re going to downgrade to 8.5.0 to fix this as it wasn’t happening back then. However, before we do, is there some kind of diagnostic log that will help you, help me, help you? 😃

Thanks, and I know this is vague, not sure where to even start here.

[15:24:18]W:		 [Docker Run] [111:1207/202418.627106:ERROR:bus.cc(392)] Failed to connect to the bus: Address does not contain a colon
[15:24:19] :		 [Docker Run] The Test Runner unexpectedly exited via a exit event with signal SIGSEGV
[15:24:19] :		 [Docker Run] 
[15:24:19] :		 [Docker Run] Please search Cypress documentation for possible solutions:
[15:24:19] :		 [Docker Run] 
[15:24:19] :		 [Docker Run] https://on.cypress.io
[15:24:19] :		 [Docker Run] 
[15:24:19] :		 [Docker Run] Check if there is a GitHub issue describing this crash:
[15:24:19] :		 [Docker Run] 
[15:24:19] :		 [Docker Run] https://github.com/cypress-io/cypress/issues
[15:24:19] :		 [Docker Run] 
[15:24:19] :		 [Docker Run] Consider opening a new issue.
[15:24:19] :		 [Docker Run] 
[15:24:19] :		 [Docker Run] ----------
[15:24:19] :		 [Docker Run] 
[15:24:19] :		 [Docker Run] Platform: linux-x64 (Debian - 10.10)
[15:24:19] :		 [Docker Run] Cypress Version: 9.1.1
[15:24:19] :		 [Docker Run] info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[15:24:19]W:		 [Docker Run] error Command failed with exit code 1.
[15:24:19]W:		 [Docker Run] Error: Command failed with exit code 1: yarn test:cypress --reporter teamcity --config video=false,defaultCommandTimeout=10000 --record false
[15:24:19]W:		 [Docker Run]     at makeError (/workspace/Sites/node_modules/start-server-and-test/node_modules/execa/lib/error.js:60:11)
[15:24:19]W:		 [Docker Run]     at handlePromise (/workspace/Sites/node_modules/start-server-and-test/node_modules/execa/index.js:118:26)
[15:24:19]W:		 [Docker Run]     at processTicksAndRejections (node:internal/process/task_queues:96:5) {
[15:24:19]W:		 [Docker Run]   shortMessage: 'Command failed with exit code 1: yarn test:cypress --reporter teamcity --config video=false,defaultCommandTimeout=10000 --record false',
[15:24:19]W:		 [Docker Run]   command: 'yarn test:cypress --reporter teamcity --config video=false,defaultCommandTimeout=10000 --record false',
[15:24:19]W:		 [Docker Run]   escapedCommand: '"yarn test:cypress --reporter teamcity --config video=false,defaultCommandTimeout=10000 --record false"',
[15:24:19]W:		 [Docker Run]   exitCode: 1,
[15:24:19]W:		 [Docker Run]   signal: undefined,
[15:24:19]W:		 [Docker Run]   signalDescription: undefined,
[15:24:19]W:		 [Docker Run]   stdout: undefined,
[15:24:19]W:		 [Docker Run]   stderr: undefined,
[15:24:19]W:		 [Docker Run]   failed: true,
[15:24:19]W:		 [Docker Run]   timedOut: false,
[15:24:19]W:		 [Docker Run]   isCanceled: false,
[15:24:19]W:		 [Docker Run]   killed: false
[15:24:19]W:		 [Docker Run] }
[15:24:19]W:		 [Docker Run] error Command failed with exit code 1.
[15:24:19] :		 [Docker Run] info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Desired behavior

Do not throw the SIGSEGV.

Test code to reproduce

It can happen on any test, at any time, in our 850+ test test suite.

Cypress Version

9.1.1

Other

It doesn’t seem to happen if we run on Windows, and we have a parallel set of Component tests (about 100) that have yet to show the issue and they’re run exactly the same way in the same Docker container, just as component tests.

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 138
Comments: 64 (8 by maintainers)

Commits related to this issue

Specify Chrome browser for https://github.com/cypress-io/cypress/issues/19299 — committed to bonnie/ten-cent-teacakes by bonnie 2 years ago

Most upvoted comments

Please tap on 👍 reaction on first message in this issue to get attention of Cypress team 😃

+21

n10v on Jan 20, 2022

So I spent a lot of time looking deep into the internals of Electron + Chromium to verify this, be extra 100% sure: these errors never cause problems, and are a red herring. There are sometimes issues where cypress fails to launch, where it fails to connect to electron and to browsers, but these errors aren’t the cause.

That’s why there hasn’t been much motion on this issue - we were pretty sure this was the case, but didn’t have time to verify it 100% until now. If you want the technical details of why these were being emitted, take a look at the PR for an explanation. They’ll be silenced in the next cypress release, but this won’t fix any existing issues people are running into.

+19

BlueWinds on Apr 6, 2022

@jennifer-shehane what’s the status of this showstopper?

+17

tnrich on Mar 9, 2022

I’m using 9.2.0 and I see these warnings:

[43:1227/121552.068477: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
[43:1227/121552.072800:ERROR:bus.cc(392)] Failed to connect to the bus: Address does not contain a colon                                                      
[43:1227/121552.072876:ERROR:bus.cc(392)] Failed to connect to the bus: Address does not contain a colon                                                      
[215:1227/121552.088414:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is

+16

vibaiher-qatium on Dec 27, 2021

STILL A PROBLEM!

+15

Cpt-Falcon on Apr 6, 2022

As a note: “Me too” comments are not particularly useful. We look at reactions to issues when assessing seriousness - 132 thumbs up means it’s very important to the community!

By all means hold conversation and discussion, and if something hasn’t been updated in weeks, a bump may be appropriate. But “Me too” multiple times a day make it harder for everyone to find the meat of issues.

+11

BlueWinds on Apr 6, 2022

I’m getting these when running as a github action:

[357:1229/202813.707201:ERROR:bus.cc(392)] Failed to connect to the bus: Address does not contain a colon
[357:1229/202813.707294:ERROR:bus.cc(392)] Failed to connect to the bus: Address does not contain a colon
[357:1229/202813.715586: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
[518:1229/202813.750545:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is

Using cypress 9.2.0, chrome 96, node version 12.22.8

+11

joel-rw on Dec 29, 2021

Any word on the status of this from the cypress team 😃 ?

tnrich on Apr 6, 2022

ok, I did some research and ran the container with debugging and exactly the same test spec. cypress/included:9.5.2

====================================================================================================
  (Run Finished)
       Spec                                              Tests  Passing  Failing  Pending  Skipped  
  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ ✔  myTest.spec.js                 00:14        1        1        -        -        - │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘
    ✔  All specs passed!                        00:14        1        1        -        -        -  
  cypress:server:cypress about to exit with code 0 +29s
  cypress:server:browsers browsers.kill called with no active instance +2s
  cypress:proxy:http:util:prerequests metrics: { browserPreRequestsReceived: 40, proxyRequestsReceived: 37, immediatelyMatchedRequests: 32, eventuallyReceivedPreRequest: [ { url: 'http://localhost:8080/app/chunk-common.js', afterMs: 1 }, { url: 'http://localhost:8080/app/img/pxc_logo_transparent.png', afterMs: 4 }, { url: 'https://mpp.gocloud-dev.europe.phoenixcontact.com/graphql', afterMs: 2 } ], neverReceivedPreRequest: [ { url: 'https://redirector.gvt1.com/edgedl/chrome/dict/en-us-9-0.bdic' }, { url: '[https://r1---sn-4g5ednly.gvt1.com/edgedl/chrome/dict/en-us-9-0.bdic?cms_redirect=yes&mh=I2&mip=62.157.123.151&mm=28&mn=sn-4g5ednly&ms=nvh&mt=1648211845&mv=u&mvi=1&pl=26&rmhost=r2---sn-4g5ednly.gvt1.com&shardbypass=sd&smhost=r1---sn-4g5edn6r.gvt1.com'](https://r1---sn-4g5ednly.gvt1.com/edgedl/chrome/dict/en-us-9-0.bdic?cms_redirect=yes&mh=I2&mip=62.157.123.151&mm=28&mn=sn-4g5ednly&ms=nvh&mt=1648211845&mv=u&mvi=1&pl=26&rmhost=r2---sn-4g5ednly.gvt1.com&shardbypass=sd&smhost=r1---sn-4g5edn6r.gvt1.com%27) } ] } +0ms
2022-03-25T12:45:39.668Z cypress:cli child event fired { event: 'exit', code: 0, signal: null }
2022-03-25T12:45:39.668Z cypress:cli child event fired { event: 'close', code: 0, signal: null }
2022-03-25T12:45:39.668Z cypress:cli Stopping Xvfb
node:events:498
      throw er; // Unhandled 'error' event
      ^
Error: spawn ps ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:478:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
    at onErrorNT (node:internal/child_process:478:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn ps',
  path: 'ps',
  spawnargs: [ '-A', '-o', 'ppid,pid,stat,comm' ]
}
Uploading artifacts for failed job
00:01
Uploading artifacts...
test/cypress/videos/**/*.mp4: found 1 matching files and directories 
WARNING: test/cypress/screenshots/**/*.png: no matching files 
Uploading artifacts as "archive" to coordinator... ok  id=231505 responseStatus=201 Created token=zwkLyLwQ
Uploading artifacts...
cypress_*.xml: found 1 matching files and directories 
Uploading artifacts as "junit" to coordinator... ok  id=231505 responseStatus=201 Created token=zwkLyLwQ
Cleaning up project directory and file based variables
00:01
ERROR: Job failed: exit code 1

and then cypress/included:8.7.0

====================================================================================================
  (Run Finished)
       Spec                                              Tests  Passing  Failing  Pending  Skipped  
  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ ✔  myTest.spec.js                 00:10        1        1        -        -        - │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘
    ✔  All specs passed!                        00:10        1        1        -        -        -  
  cypress:server:cypress about to exit with code 0 +25s
  cypress:server:browsers browsers.kill called with no active instance +1s
  cypress:proxy:http:util:prerequests metrics: { browserPreRequestsReceived: 40, proxyRequestsReceived: 37, immediatelyMatchedRequests: 32, eventuallyReceivedPreRequest: [ { url: 'http://localhost:8080/app/vendor.js', afterMs: 1 }, { url: 'http://localhost:8080/app/app.js', afterMs: 4 }, { url: 'http://localhost:8080/app/img/pxc_logo_transparent.png', afterMs: 3 } ], neverReceivedPreRequest: [ { url: 'https://redirector.gvt1.com/edgedl/chrome/dict/en-us-9-0.bdic' }, { url: '[https://r3---sn-4g5ednde.gvt1.com/edgedl/chrome/dict/en-us-9-0.bdic?cms_redirect=yes&mh=I2&mip=62.157.123.168&mm=28&mn=sn-4g5ednde&ms=nvh&mt=1648213220&mv=m&mvi=3&pl=26&rmhost=r5---sn-4g5ednde.gvt1.com&shardbypass=sd&smhost=r1---sn-4g5edn6r.gvt1.com'](https://r3---sn-4g5ednde.gvt1.com/edgedl/chrome/dict/en-us-9-0.bdic?cms_redirect=yes&mh=I2&mip=62.157.123.168&mm=28&mn=sn-4g5ednde&ms=nvh&mt=1648213220&mv=m&mvi=3&pl=26&rmhost=r5---sn-4g5ednde.gvt1.com&shardbypass=sd&smhost=r1---sn-4g5edn6r.gvt1.com%27) } ] } +0ms
2022-03-25T13:05:12.523Z cypress:cli child event fired { event: 'exit', code: 0, signal: null }
2022-03-25T13:05:12.523Z cypress:cli child event fired { event: 'close', code: 0, signal: null }
2022-03-25T13:05:12.523Z cypress:cli Stopping Xvfb
Saving cache for successful job
00:18
Creating cache someBranch...
node_modules/: found 79138 matching files and directories 
No URL provided, cache will be not uploaded to shared cache server. Cache will be stored only locally. 
Created cache
Uploading artifacts for successful job
00:01
Uploading artifacts...
test/cypress/videos/**/*.mp4: found 1 matching files and directories 
WARNING: test/cypress/screenshots/**/*.png: no matching files 
Uploading artifacts as "archive" to coordinator... ok  id=231527 responseStatus=201 Created token=vmxNBXBw
Uploading artifacts...
cypress_*.xml: found 1 matching files and directories 
Uploading artifacts as "junit" to coordinator... ok  id=231527 responseStatus=201 Created token=vmxNBXBw
Cleaning up project directory and file based variables
Job succeeded

The error raises when Xvfb is stopped… maybe it´s not a cypress related issue, but at least the cypress/included:9.5.2 container is broken.

I downgraded to cypress 8.7.0 again.

mobsean on Mar 25, 2022

Cypress 9.5.2 [18:0316/124110.484585:ERROR:bus.cc(392)] Failed to connect to the bus: Address does not contain a colon

cjonstrup on Apr 6, 2022

Same issue here (version 9.3.1) but in our CI pipeline, which also caused excessive run time (+5min) for the cypress tests. Reverted to version 8.3.1 and the issue is resolved. None of the issues above resolved it otherwise

jana-levesque on Jan 27, 2022

Same issue in Cypress 9.1.1 [STARTED] Task without title. [SUCCESS] Task without title. [853:0112/180551.155229:ERROR:bus.cc(392)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [853:0112/180551.157544:ERROR:bus.cc(392)] Failed to connect to the bus: Address does not contain a colon [853:0112/180551.157587:ERROR:bus.cc(392)] Failed to connect to the bus: Address does not contain a colon [1009:0112/180551.209964:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is

balawej on Jan 12, 2022

These dbus errors will be silenced in the next Cypress release. This will not solve SIGSEGV errors, since they were not caused by this message to begin with.

Sorry! There are quite a number of open issues discussing faults in CI / docker - I encourage people who’ve found this issue to search other github issues, where you’re more likely to find solutions, or at least better able to provide more targeted debugging so we can tackle the real causes.

BlueWinds on Apr 7, 2022

I encountered the same issue with GitHub Actions + Docker, but I was able to workaround (locally) using the following post.

Cypress: 9.2.1
Docker Container: cypress/browsers:node16.13.0-chrome95-ff94
Node: v16.13.0
Chrome Webdriver: 95.0.4638.69

Workaround Steps

Although the recommendation is that you run the container with --user 1001, I entered the container through an interactive shell and changed permissions (logged in as root).

$ chmod 777 -R /root
$ chmod 777 -R node_modules/

Once done, I proceeded to run the Cypress tests using the following:

$ nohup yarn start & (i.e. start React app in foreground)

$ Xvfb -screen 0 1920x1080x24 :99 & export DISPLAY=:99 && npx cypress run --browser chrome && pkill Xvfb

To make sure that this wasn’t a false positive, I edited my integration tests to assert a false statement, and confirmed the tests are working as intended.

       Spec                                              Tests  Passing  Failing  Pending  Skipped  
  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ ✔  app.spec.js                              00:06        1        1        -        -        - │
  ├────────────────────────────────────────────────────────────────────────────────────────────────┤
  │ ✖  Incidents/incidents.spec.js              00:22        1        -        1        -        - │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘
    ✖  1 of 2 failed (50%)                      00:28        2        1        1        -        -

Going to do some more digging and see how I can utilise this within GitHub actions - would be great for the Cypress team to provide a proper solution / patch to this.

giranm on Jan 22, 2022

I want to reiterate for those that didn’t see my comment after opening this issue.

I had all kinds of SIGSEGV issues with Cypress/Electron/Docker.

I switched to using headless Chrome and they all went away.

I get that may not be a solution for everyone, and if you think you can add value by helping the Cypress team with debug info, or reproducible test cases, definitely do that as I’m sure they’re as frustrated with these SIGSEGV errors as you are.

For me and my team, running in Chrome is fine, and we have seen no downsides.

Good luck all!

cubanx on Apr 7, 2022

+1 SIGSEV

[1965:0119/144529.699618: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")

Cypress: 9.2.1 Browser: Electron 94 (headless) Node Version: v16.5.0

azoff on Jan 19, 2022

Hi,

I´m running a CI with: cypress/included:9.5.2. and get this error in the gitlab logs: This happens with --browser chrome and with default electron browser.

[964:0325/101306.387739:ERROR:bus.cc(392)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[964:0325/101306.389313:ERROR:bus.cc(392)] Failed to connect to the bus: Address does not contain a colon
[964:0325/101306.389336:ERROR:bus.cc(392)] Failed to connect to the bus: Address does not contain a colon
[1151:0325/101306.401999:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is 
tput: unknown terminal "xterm   npm_config_loglevel warn   npm_config_unsafe_perm true"

The run finishes successful and then still drops an error on exit:

       Spec                                              Tests  Passing  Failing  Pending  Skipped  
  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ ✔  myTest.spec.js                 00:06        1        1        -        -        - │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘
    ✔  All specs passed!                        00:06        1        1        -        -        -  
node:events:498
      throw er; // Unhandled 'error' event
      ^
Error: spawn ps ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:478:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
    at onErrorNT (node:internal/child_process:478:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn ps',
  path: 'ps',
  spawnargs: [ '-A', '-o', 'ppid,pid,stat,comm' ]
}
Uploading artifacts...
test/cypress/videos/**/*.mp4: found 1 matching files and directories 
WARNING: test/cypress/screenshots/**/*.png: no matching files 
Uploading artifacts as "archive" to coordinator... ok  id=231064 responseStatus=201 Created token=U-Aj24KV
Uploading artifacts...
cypress_*.xml: found 1 matching files and directories 
Uploading artifacts as "junit" to coordinator... ok  id=231064 responseStatus=201 Created token=U-Aj24KV
Cleaning up project directory and file based variables
00:01
ERROR: Job failed: exit code 1

mobsean on Mar 25, 2022

+1 in Gitlab CI Pipeline with Image cypress/included:9.5.0

jonsalvas on Mar 1, 2022

Same issue through our Gitlab pipeline on Cypress 9.3.1 / Node 16.13.1

sylvaindubus on Feb 4, 2022

Same happening here, I was following this: https://docs.cypress.io/guides/continuous-integration/gitlab-ci#Basic-Setup

Cypress: 9.3.0 Browser: chrome85-ff81 Node Version: 12.14.1

JCraigWasTaken on Jan 14, 2022

I’m getting [10195:0324/092959.801981: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") with 9.5.2

manv6 on Apr 6, 2022

I’ve had to back track to 7.6.0, this is horrible.

nimo-juice on Apr 6, 2022

I am having the same error as above but the tests are executing as expected. I am running my tests in a Pod on K8s and at first the tests were running indefinitely. Then I’ve found out somwhere that headless tests are consuming a lot of resources. So after I configured my Pod template spec resources to request cpu to “1” and memory to “1Gi” and limit cpu to “2” and memory to “4Gi” my tests are running fine also with the error written above. Here is an example of my Pod template:

apiVersion: v1
kind: Pod
metadata:
  namespace: jenkins
spec:
  containers:
  - name: cypress
    image: cypress/browsers:node16.13.2-chrome97-ff96
    imagePullPolicy: Always
    resources:
      requests:
        cpu: "1"
        memory: "1Gi"
      limits:
        cpu: "2"
        memory: "4Gi"

So to put in less words, if you have an option, try increasing the resources of whatever you are running your tests in. Hope it helps!

fbele on Mar 4, 2022

I’m seeing the same with latest cypress + github actions. Tests don’t crash, but they do seem to be hanging indefinitely - I’m not sure if THIS is the cause.

Jacek-fstack on Feb 7, 2022

same here in our ci 😦

[STARTED] Task without title. [SUCCESS] Task without title. [328:0120/115656.474194: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 [328:0120/115656.477331: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") [328:0120/115656.477487: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") [328:0120/115656.498674:ERROR:zygote_host_impl_linux.cc(263)] Failed to adjust OOM score of renderer with pid 499: Permission denied (13) [499:0120/115656.512083:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is

Platform: linux-x64 (Debian - 10.11) Cypress Version: 9.3.1

eLenoAr on Jan 20, 2022

I have the same issue with cypress 9.1.1, randomly the execution unexpectedly exits with sigsev, rolling it back to 8.4.0 solved the problem, also I noticed that this message shows up between every spec file Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") but it doesn’t happen in version 8.4.0, we use cypress/base:12.16.0 image in github actions.

VicenteRuizWefoxgroup on Dec 9, 2021