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

cubanx · 2021-12-07T20:36:40Z

UPDATE [by Cypress Team]: Please see #19299 (comment) for details. `Failed to connect to the bus` is a harmless message and will be silenced in future Cypress releases.

In addition, see #19299 (comment) 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.

The text was updated successfully, but these errors were encountered:

Venkateshkumar1234 · 2021-12-09T05:37:39Z

Facing the same issue in 9.1.1

Issue resolved after I downgraded the cypress to 8.3.0.

VicenteRuizWefoxgroup · 2021-12-09T15:57:05Z

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.

cubanx · 2021-12-09T16:48:39Z

BTW, for others on here commenting, I think this issue and fix might help us:
#9220

It's committed but not yet released.

I know it's an old issue, but the fix way at the bottom is new.

Hopefully we'll get it "soon" :)

cubanx · 2021-12-09T17:30:53Z

Also, I switched my headless runs from using headless electron to headless chrome and the issue seems to have abated.

YMMV :)

vibaiher-qatium · 2021-12-27T12:20:00Z

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

joel-rw · 2021-12-29T20:47:40Z

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

JoshuaKGoldberg · 2021-12-31T00:30:28Z

Here's a reproducing run on a public repo on [email protected]: https://github.com/typescript-eslint/typescript-eslint/runs/4670193488?check_suite_focus=true

$ docusaurus start
[2934:1230/222258.330171: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")
[2934:1230/222258.330260: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")
[3166:1230/222258.351104:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is 
Starting the development server...
Docusaurus website is running at "http://localhost:3000/".
Cypress could not verify that this server is running:

  > http://localhost:3000

We are verifying this server because it has been configured as your `baseUrl`.

  From Node.js Internals:
    Error: ESOCKETTIMEDOUT
        at ClientRequest.<anonymous> (/home/runner/.cache/Cypress/9.2.0/Cypress/resources/app/node_modules/@cypress/request/request.js:808:19)
        at Object.onceWrapper (node:events:513:28)

Raw logs.txt from typescript-eslint/typescript-eslint#4362

The issue does not reproduce when Cypress is downgraded to 8.3.0: https://github.com/typescript-eslint/typescript-eslint/runs/4670836053?check_suite_focus=true

cubanx · 2022-01-04T15:52:00Z

You can close this issue for my specific bug. I resolved it by switching to headless chrome.

I have not seen the SIGSEGV error since.

Thanks!

fseee · 2022-01-04T17:50:30Z

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

exactly same errors with below versions:
Cypress 9.1.1
Chrome 89 (headless)
Node Version v14.16.0

SadiqRahim · 2022-01-07T11:43:27Z

Hi there, do we have an update on this yet? I just upgraded to the cypress image "cypress/included:9.2.0" and not able to run the tests on Jenkins anymore. This works fine when I downgraded to 8.4.0 as suggested by @VicenteRuizWefoxgroup. re: issue on #9220 appears to be closed. Does anyone know whats going on?

cjonstrup · 2022-01-11T12:15:12Z

Cypress 9.2.1
[18:0111/121438.553429:ERROR:bus.cc(392)] Failed to connect to the bus: Address does not contain a colon

darul75 · 2022-01-11T12:39:52Z

Same issue in 8.6.0 ;)

cjchenPG · 2022-01-12T18:46:45Z

I'm seeing the same issue in Cypress 9.1.1.

balawej · 2022-01-12T18:50:09Z

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

leonardofaria · 2022-01-12T20:51:27Z

Same happening here (docker)

Cypress: 9.2.1
Browser: Electron 94 (headless)
Node Version: v16.5.0 (/usr/local/bin/node)

patrickmichalina · 2022-01-13T06:20:51Z

~~I am seeing the same error all of a sudden. Upgrading my docker image to cypress/browsers:node16.13.0-chrome95-ff94 seems to have fixed it though.~~

Nevermind. Still broken.

JCraigWasTaken · 2022-01-14T15:58:58Z

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

n10v · 2022-01-17T08:18:04Z

The same we have in CI after update from 8.0.0 to 9.2.1.

Cypress: 9.2.1
Browser: Electron 94 (headless)
Node Version: v16.5.0 (/usr/local/bin/node)

azoff · 2022-01-19T17:30:00Z

+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

wqsandoval · 2022-01-19T17:38:52Z

Had the same problem using ^8.3.0 on package.json. Fixed by downgrading to 8.3.0

eLenoAr · 2022-01-20T11:55:20Z

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

n10v · 2022-01-20T12:57:36Z

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

giranm · 2022-01-22T23:15:14Z

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.

jana-levesque · 2022-01-27T19:13:10Z

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

mobsean · 2022-03-25T09:36:18Z

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 · 2022-03-25T13:18:12Z

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.

iammike · 2022-04-05T21:09:10Z

Also seeing this problem. Crops up for me at 8.6.0 so reverting to 8.5.0 is my answer.

BlueWinds · 2022-04-06T16:36:50Z

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.

BlueWinds · 2022-04-06T20:18:29Z

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.

cypress-bot · 2022-04-07T17:46:27Z

The code for this is done in cypress-io/cypress#20939, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

BlueWinds · 2022-04-07T17:53:21Z

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.

cubanx · 2022-04-07T18:44:43Z

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!

anuboby · 2022-04-07T22:14:51Z

Switching to headless Chrome and errors are gone for us too.

theslantedroom · 2022-04-08T19:11:45Z

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!

Thank you in advance! Do you have any direction as to how to switch to chrome headless for running in github ci via github action?

cypress-bot · 2022-04-11T19:05:34Z

Released in 9.5.4.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v9.5.4, please open a new issue.

cubanx changed the title ~~Failed to connect to the bus: Address does not contain a colon throws a SIGSEGV error~~ Failed to connect to the bus: Address does not contain a colon throws a SIGSEGV error Dec 7, 2021

cubanx changed the title ~~Failed to connect to the bus: Address does not contain a colon throws a SIGSEGV error~~ "Failed to connect to the bus: Address does not contain a colon" throws a SIGSEGV error Dec 7, 2021

giranm mentioned this issue Jan 22, 2022

Simple test working in Electron but not Chrome cypress-io/cypress-docker-images#149

Closed

cypress-bot bot added the stage: backlog label Jan 26, 2022

cypress-bot bot added stage: to do and removed stage: backlog labels Feb 1, 2022

This comment was marked as duplicate.

Sign in to view

This comment was marked as spam.

Sign in to view

JoshuaKGoldberg mentioned this issue Mar 26, 2022

Website tests flake: ESOCKETTIMEDOUT typescript-eslint/typescript-eslint#4739

Closed

jennifer-shehane assigned BlueWinds Mar 29, 2022

cypress-bot bot added stage: to do and removed stage: backlog labels Mar 29, 2022

BlueWinds mentioned this issue Apr 6, 2022

fix: silence dbus errors #20939

Merged

2 tasks

cypress-bot bot added the stage: needs review The PR code is done & tested, needs review label Apr 6, 2022

BlueWinds closed this as completed in #20939 Apr 7, 2022

cypress-bot bot added stage: pending release and removed stage: work in progress labels Apr 7, 2022

cypress-bot bot removed the stage: needs review The PR code is done & tested, needs review label Apr 7, 2022

This was referenced Apr 7, 2022

Docker image 8.6.0 cypress-io/cypress-docker-images#543

Closed

dbus warnings with 9.0.0 image cypress-io/cypress-docker-images#555

Closed

cypress-bot bot removed the stage: pending release label Apr 11, 2022

cypress-bot bot locked as resolved and limited conversation to collaborators Apr 11, 2022

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

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

Comments

cubanx commented Dec 7, 2021 • edited by BlueWinds Loading

UPDATE [by Cypress Team]: Please see #19299 (comment) for details. Failed to connect to the bus is a harmless message and will be silenced in future Cypress releases.

Current behavior

Desired behavior

Test code to reproduce

Cypress Version

Other

Venkateshkumar1234 commented Dec 9, 2021 • edited Loading

VicenteRuizWefoxgroup commented Dec 9, 2021

cubanx commented Dec 9, 2021

cubanx commented Dec 9, 2021

vibaiher-qatium commented Dec 27, 2021

joel-rw commented Dec 29, 2021

JoshuaKGoldberg commented Dec 31, 2021 • edited Loading

cubanx commented Jan 4, 2022

fseee commented Jan 4, 2022

SadiqRahim commented Jan 7, 2022

cjonstrup commented Jan 11, 2022

darul75 commented Jan 11, 2022

cjchenPG commented Jan 12, 2022

balawej commented Jan 12, 2022

leonardofaria commented Jan 12, 2022

patrickmichalina commented Jan 13, 2022 • edited Loading

JCraigWasTaken commented Jan 14, 2022

n10v commented Jan 17, 2022

azoff commented Jan 19, 2022

wqsandoval commented Jan 19, 2022

eLenoAr commented Jan 20, 2022 • edited Loading

n10v commented Jan 20, 2022

giranm commented Jan 22, 2022 • edited Loading

Workaround Steps

jana-levesque commented Jan 27, 2022

This comment was marked as duplicate.

This comment was marked as duplicate.

This comment was marked as spam.

mobsean commented Mar 25, 2022

mobsean commented Mar 25, 2022

iammike commented Apr 5, 2022

BlueWinds commented Apr 6, 2022 • edited Loading

BlueWinds commented Apr 6, 2022 • edited Loading

cypress-bot bot commented Apr 7, 2022

BlueWinds commented Apr 7, 2022

cubanx commented Apr 7, 2022 • edited Loading

anuboby commented Apr 7, 2022

theslantedroom commented Apr 8, 2022

cypress-bot bot commented Apr 11, 2022

cubanx commented Dec 7, 2021 •

edited by BlueWinds

Loading

UPDATE [by Cypress Team]: Please see #19299 (comment) for details. `Failed to connect to the bus` is a harmless message and will be silenced in future Cypress releases.

Venkateshkumar1234 commented Dec 9, 2021 •

edited

Loading

JoshuaKGoldberg commented Dec 31, 2021 •

edited

Loading

patrickmichalina commented Jan 13, 2022 •

edited

Loading

eLenoAr commented Jan 20, 2022 •

edited

Loading

giranm commented Jan 22, 2022 •

edited

Loading

BlueWinds commented Apr 6, 2022 •

edited

Loading

BlueWinds commented Apr 6, 2022 •

edited

Loading

cubanx commented Apr 7, 2022 •

edited

Loading