"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.

[bogem]

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

[BlueWinds]

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.