Firefox 124 + Cypress 13.7.1 The browser never connected. Something is wrong. The tests cannot run. Aborting... after first test with multiple tests on CI #29190
Comments
|
I tried to reproduce your issue using the repo https://github.com/cypress-io/cypress-example-kitchensink. The workflow I set up to use Firefox failed with Firefox I have a couple of comments which may or may not help:
|
jennifer-shehane
added
the
stage: needs information
|
#29172 was supposed to fix this issue on cypress First test passes then second tests fails to connect to the browser: I'll try to provide a minimal reproducible sample |
|
@MikeMcC399 May I request you to try again with firefox module.exports = {
// ... some config
e2e: {
// ... some config
// specify user agent:
userAgent: 'Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/114.0'
}
}For me it fails with the user agent string, and works when I remove it |
|
Your Firefox user agent string is not consistent with Firefox |
|
|
Are you also specifying Edit: or something non-null. |
|
@MikeMcC399 from my expectation the user agent string itself shouldn't change how cypress behaves. We use it to make sure our app will detect that it's an unsupported browser during E2E, and I'm sure that other users will do the same. It's a lot faster than having to manage multiple firefox binaries when all we need is to change the UA string. I'm not even sure why cypress would allow us to change the UA string if it breaks cypress itself. Any chance we can expect a more solid support for firefox >124? |
|
Thanks for your explanation!
|
|
@MikeMcC399 I can definitely say we use a specific userAgent in our FF tests as well, making it break for us as well, only when running against CI (only because we only set this in the GH action workflow for the FF run) @gsouf thanks for bringing this up! This was driving me insane |
|
looking at our history, we can probably just update the userAgent used to 124.0 in the custom config. Our issue appeared to be something around the |
I opted to use the We could likely pass in the binary version detected in the app at time of launch and forward that to the extension request, but that seemed somewhat involved and unnecessary. It can be done, but it would need to be baked into Cypress itself and it likely a lot easier to adapt your UA to include the version in which is being run. |
jennifer-shehane
added
stage: needs investigating
|
@AtofStryker thanks for the details. But knowing that does it make sense to expose the ability to change the user agent? It seems that as long as an user is specifying a UA it's potentially going to break the cypress runtime itself. For which use case, in the first place, does cypress allow users to configure a custom user agent? |
@gsouf Cypress allows the use of custom user agents. You should be able to change the user agent without being impacted. That currently does not work in this case, so we are exploring solutions where we don't rely on the user agent to interpret the version for the fix. Either we can forward the version from the binary, or we can apply the fix more broadly. I should be looking into this shortly! |
|
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
cypress-bot
bot
removed
the
stage: needs investigating
Current behavior
After upgrading to 13.7.1 to fix the Firefox 124 issue, we confirmed that local runs of
openandrunwork to run tests in Firefox with multiple specs synchronously.But, overnight on the Github CI workflow action, we are continuing to see failures on any jobs that have multiple specs for Firefox only. Our Github action uses
@cypress/github-actionsv5with the followingOutput without debug showing the first test succeeding but the second test failing/aborting:
Chrome which runs on the same GH runner, same OS, using
@cypress/github-actionsv5has no issuesDesired behavior
Running Cypress in Github Workflow against Firefox 124 with
@cypress/github-actionsv5where multiple specs run synchronously worksTest code to reproduce
Should fail running against github action on FF124 using ubuntu image with multiple specs
Cypress Version
13.7.1
Node version
v16.20.2
Operating System
ubuntu-22.04
Debug Logs
cypress:server:socket-base socket-disconnecting transport close +99ms cypress:server:socket-base socket-disconnect transport close +0ms cypress:launcher:browsers firefox stdout: Stopped devtools server on 42925 +53ms cypress:launcher:browsers firefox stdout: 1711204983446 Marionette INFO Stopped listening on port 41353 +3ms cypress:server:util:socket_allowed allowed socket closed, removing { localPort: 35270 } +193ms cypress:server:util:socket_allowed allowed socket closed, removing { localPort: 35306 } +0ms cypress:server:util:socket_allowed allowed socket closed, removing { localPort: 35302 } +2ms cypress:server:util:socket_allowed allowed socket closed, removing { localPort: 35284 } +31ms cypress:server:util:socket_allowed allowed socket closed, removing { localPort: 35298 } +0ms cypress:server:util:socket_allowed allowed socket closed, removing { localPort: 35320 } +45ms cypress:server:util:socket_allowed allowed socket closed, removing { localPort: 51772 } +63ms cypress:server:util:socket_allowed allowed socket closed, removing { localPort: 51804 } +31ms cypress:server:util:socket_allowed allowed socket closed, removing { localPort: 35244 } +76ms cypress:server:util:socket_allowed allowed socket closed, removing { localPort: 51834 } +3ms cypress:server:util:socket_allowed allowed socket closed, removing { localPort: 35262 } +1ms cypress:server:util:socket_allowed allowed socket closed, removing { localPort: 51830 } +1ms cypress:server:util:socket_allowed allowed socket closed, removing { localPort: 35148 } +1ms cypress:server:util:socket_allowed allowed socket closed, removing { localPort: 35134 } +1ms cypress:server:browsers:cri-client disconnected, starting retries to reconnect... { closed: false, target: 'ws://127.0.0.1:44279/devtools/browser/00d49155-e24f-4458-80a1-76e2b78c3ede' } +1m cypress:server:browsers:cri-client disconnected, attempting to reconnect... { retryIndex: 1, closed: false, target: 'ws://127.0.0.1:44279/devtools/browser/00d49155-e24f-4458-80a1-76e2b78c3ede' } +0ms cypress:server:browsers:cri-client connecting { connected: false, target: 'ws://127.0.0.1:44279/devtools/browser/00d49155-e24f-4458-80a1-76e2b78c3ede' } +1ms cypress:server:browsers:cri-client could not reconnect, retrying... { closed: false, target: 'ws://127.0.0.1:44279/devtools/browser/00d49155-e24f-4458-80a1-76e2b78c3ede', err: Error: socket hang up at connResetException (node:internal/errors:720:14) at Socket.socketOnEnd (node:_http_client:525:23) at Socket.emit (node:events:526:35) at endReadableNT (node:internal/streams/readable:1359:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { code: 'ECONNRESET' } } +16ms cypress:server:browsers:firefox-util firefox: reconnecting CDP +509ms cypress:server:browsers:cri-client closing cri client { closed: false, target: '62f586a6-876e-4bd5-b8dc-38bb9b96257a' } +5ms cypress:server:browsers:cri-client closed cri client { closed: true, target: '62f586a6-876e-4bd5-b8dc-38bb9b96257a' } +0ms cypress:server:browsers:browser-cri-client Attaching to target url about:blank +1m cypress:server:browsers:cri-client enqueueing command { command: 'Target.getTargets', params: undefined } +0ms cypress:server:browsers:cri-client disconnected, attempting to reconnect... { retryIndex: 2, closed: false, target: 'ws://127.0.0.1:44279/devtools/browser/00d49155-e24f-4458-80a1-76e2b78c3ede' } +97ms cypress:server:browsers:cri-client connecting { connected: false, target: 'ws://127.0.0.1:44279/devtools/browser/00d49155-e24f-4458-80a1-76e2b78c3ede' } +0ms cypress:server:browsers:cri-client could not reconnect, retrying... { closed: false, target: 'ws://127.0.0.1:44279/devtools/browser/00d49155-e24f-4458-80a1-76e2b78c3ede', err: Error: connect ECONNREFUSED 127.0.0.1:44279 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '127.0.0.1', port: 44279 } } +3ms cypress:server:browsers:cri-client disconnected, attempting to reconnect... { retryIndex: 3, closed: false, target: 'ws://127.0.0.1:44279/devtools/browser/00d49155-e24f-4458-80a1-76e2b78c3ede' } +101ms cypress:server:browsers:cri-client connecting { connected: false, target: 'ws://127.0.0.1:44279/devtools/browser/00d49155-e24f-4458-80a1-76e2b78c3ede' } +0ms cypress:server:browsers:cri-client could not reconnect, retrying... { closed: false, target: 'ws://127.0.0.1:44279/devtools/browser/00d49155-e24f-4458-80a1-76e2b78c3ede', err: Error: connect ECONNREFUSED 127.0.0.1:44279 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '127.0.0.1', port: 44279 } } +3ms cypress:launcher:browsers firefox exited: { code: 0, signal: null } +669ms cypress:server:browsers browser instance exit event received { code: 0, signal: null } +729ms cypress:server:preprocessor removeFile /home/runner/work/vision-web/vision-web/e2e-tests/cypress/specs/parallel/knowledgebase/collections.js +1m cypress:server:preprocessor base emitter plugin close event +0ms cypress:server:preprocessor base emitter native close event +1ms cypress:server:preprocessor base emitter native close event +1ms cypress:server:browsers:firefox closing remote interface client +15s cypress:server:browsers:cri-client not closing, cri client is already closed { closed: true, target: '62f586a6-876e-4bd5-b8dc-38bb9b96257a' } +17ms cypress:server:browsers:cri-client closing cri client { closed: false, target: 'ws://127.0.0.1:44279/devtools/browser/00d49155-e24f-4458-80a1-76e2b78c3ede' } +0ms cypress:server:browsers:cri-client closed cri client { closed: true, target: 'ws://127.0.0.1:44279/devtools/browser/00d49155-e24f-4458-80a1-76e2b78c3ede' } +0ms cypress:webpack close /home/runner/work/vision-web/vision-web/e2e-tests/cypress/specs/parallel/knowledgebase/collections.js +1m cypress:server:browsers:cri-client disconnected, not reconnecting because client is closed { closed: true, target: 'ws://127.0.0.1:44279/devtools/browser/00d49155-e24f-4458-80a1-76e2b78c3ede' } +85ms cypress:server:browsers browsers.kill called with no active instance +59s Timed out waiting for the browser to connect. Retrying... cypress:server:browsers browsers.kill called with no active instance +1m The browser never connected. Something is wrong. The tests cannot run. Aborting... cypress:server:run onError +1m The browser never connected. Something is wrong. The tests cannot run. Aborting... cypress:server:run received project end +1ms cypress:server:run received videoController { videoController: undefined } +0ms cypress:server:run spec results: { error: 'The browser never connected. Something is wrong. The tests cannot run. Aborting...', reporter: undefined, reporterStats: null, screenshots: [], spec: { absolute: '/home/runner/work/vision-web/vision-web/e2e-tests/cypress/specs/parallel/knowledgebase/knowledgebase-search.js', fileExtension: '.js', fileName: 'knowledgebase-search', name: 'knowledgebase-search.js', relative: 'cypress/specs/parallel/knowledgebase/knowledgebase-search.js' }, stats: { duration: 0, endedAt: '2024-03-23T14:46:03.416Z', failures: 1, passes: 0, pending: 0, skipped: 0, startedAt: '2024-03-23T14:46:03.416Z', suites: 0, tests: 0 }, tests: [], video: null } +1ms cypress:server:run execute after:spec +0msOther
No response
The text was updated successfully, but these errors were encountered: