Closed bilarallen closed 1 year ago
Hi @bilarallen , Can you provide more context? What troubleshooting steps have you tried? Does this test run locally fine? I understand you can't share this private repo, but can you make a reproducible example in https://github.com/cypress-io/cypress-test-tiny? Without a reproducible example it is unlikely we will be able to help with your problem.
Hi @nagash77 yes this works fine on my local but when running in the CI using Jenkins it randomly occurs in some spec. Apologies but this issue seems to be just on our project and can't reproduce it outside of our test. Would it be okay if I'll just put the whole Cypress debug logs in a file including the environment info, these would be huge logs but I guess this will suffice for your investigation.
@bilarallen I see in your description you are using 5 VMs to run these in parallel. What happens when you run the suite on a single VM in jenkins? I have a feeling whatever mechanisms you are using to try and run in parallel might be adding noise to the possible problems.
@nagash77 Yes we're using AWS ec2 fleet with 5 instances running in our Jenkins where our automation run in parallel. I haven't tried to run our test only in one VM as our test count is really huge and this occurs randomly in a single different VM, perhaps I can share it here the full logs. The error occurs in lines 18325 to 18373 Cypress_Issue_26765_Full_Logs.txt
Here's the envi info:
System:
OS: Linux 5.15 Debian GNU/Linux 10 (buster) 10 (buster)
CPU: (4) x64 Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
Memory: 11.19 GB / 15.44 GB
Container: Yes
Shell: 5.0.3 - /bin/bash
Binaries:
Node: 14.16.0 - /usr/local/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 6.14.11 - /usr/local/bin/npm
npmPackages:
@babel/eslint-parser: ^7.21.8 => 7.21.8
@currents/cli: ^4.0.3 => 4.0.3
@cypress/angular: 0.0.0-development
@cypress/mount-utils: 0.0.0-development
@cypress/react: 0.0.0-development
@cypress/react18: 0.0.0-development
@cypress/svelte: 0.0.0-development
@cypress/vue: 0.0.0-development
@cypress/vue2: 0.0.0-development
@cypress/webpack-batteries-included-preprocessor: ^2.4.0 => 2.4.0
@cypress/webpack-preprocessor: ^5.17.0 => 5.17.0
@faker-js/faker: ^7.6.0 => 7.6.0
babel-eslint: ^10.1.0 => 10.1.0
cypress: ^12.12.0 => 12.12.0
cypress-cloud: ^1.7.4 => 1.7.4
cypress-network-idle: ^1.14.2 => 1.14.2
cypress-real-events: ^1.7.6 => 1.7.6
cypress-recurse: ^1.27.0 => 1.27.0
eslint: ^8.39.0 => 8.39.0
moment: ^2.29.4 => 2.29.4
numeral: ^2.0.6 => 2.0.6
swagger-client: ^3.18.5 => 3.18.5
uuid: ^9.0.0 => 9.0.0 (8.3.2)
xvfb: ^0.4.0 => 0.4.0
npmGlobalPackages:
npm: 6.14.11
yarn: 1.22.10
Since 2 days after last upgrade (12.11 -> 12.12) I have been experiencing the same issue on CircleCI. It fails randomly, but always exactly the same test. Running Cypress tests in 5 environments simultaneously with 2 additional environments for other tests. It's a private repo too. It's rather hard to try running tests in a single environment and check the behaviour, as the test fails randomly.
Not sure what other info I can provide to help, cannot create an example, but maybe can add something?
We face the same issue, running tests on our Jenkins. The problem occurs randomly and even on random tests...
Hi @bilarallen , I see you are using cypress-cloud. This package in spite of its name is not a Cypress library and has known issue with Cypress. I would suggest you explore alternatives or try removing that dependency and seeeing if that solves your problem.
Hi @nagash77 I understand that we're not using the official reporting tool of cypress but the issue itself based on my provided logs is obviously from the cypress:server
, so I'm wondering why we need to close this issue. not to mention that @wawer77 and @headfox23 also experience this.
Same issue for us on CircleCI after upgrading to 12.12.0
Hi, @JeremieDoctrine @headfox23 @wawer77 you guys can create a new issue for this problem that we are experiencing as cypress peeps keeps closing this issue since in the logs that I have provided we used an "unofficial" cypress library even though the problem based on my logs was obviously on cypress side which I firmly believe you are also encountering. Thanks!
Hey @bilarallen , I can see it was reopened and moved to new issue today. I don't think it's useful to litter them with identical issues. We'll see :)
@wawer77 this issue status is Closed as not planned
. Let's see most likely they will close this again.
We have this same issue as well, both when running Cypress locally as well as in a GitHub Action. It is also a flaky error for us (occurs maybe one out of every 3-4 times?). We only started experiencing this after upgrading from 12.11 to 12.12, and after updating to 12.13 we still get the same error occasionally. We have reverted to 12.11 for the time being, since this recurring error prevents us from effectively using the newer versions. It also always seems to happen when one particular spec file is reached.
It seems https://github.com/cypress-io/cypress/pull/26573 may have introduced this issue in the upgrade to 12.12?
@spagnon7 please create a new ticket for this as the Cypress team keeps closing this ticket I filled, there you can include an example of the test that will show the error. @nagash77 please consider this issue as this doesn't only occur to 1 or 2 users of Cypress. 🤦 Thanks!
@spagnon7 please open a new issue with a reproducible example and the Cypress team will be happy to investigate.
Also have this problem since 12.12, it repeats in 12.13 and in 12.14
downgrading to 12.11 helps and works well as usual
Hi @DukeVoldemar please comment on this ticket https://github.com/cypress-io/cypress/issues/26900 regarding this issue and include reproducible example if you can so they can investigate this properly, else we will stick to 12.11 and can't upgrade to future versions which are not ideal for us cypress users.
Hello everyone. I am experiencing a similar problem. The following are the observations I made during the Jenkins run and local testing:
Cypress v12.12.0 The following specification intermittently passes and fails in the CI environment. Please prioritize resolving this issue as it is negatively impacting productivity.
Same Specs :
@Pipul-Pant In order to give our engineers the best chance at recreating your problem, please create a reproducible example using a fork of Cypress Test Tiny. This gives us the best chance of seeing exactly what you are seeing and being able to investigate effectively. Are you able to provide such an example that replicates this behavior?
We have the same problem with Cypress 12.12. The test execution randomly stops with the above error. It cannot be reproduced since it only happens every now and then. It also doesn't happen always at the same test ... it's just random after a new test suite is started. We run our tests inside a Windows VM manually and automatically.
We switch back to 12.11 to see if it solves this issue in the meantime.
I've just updated from latest Cypress 11 to Cypress 12.13 and got this error as well ):
@alfaproject This issue has been closed for a while - since we didn't receive a reproducible example we weren't able to troubleshoot or diagnose the issue. If you are encountering the same problem and are able to provide an example project that demonstrates the failure I would invite you to open a new issue so we can take another look
@mike-plummer I'm seeing it fairly regularly in one of my tests, using Cypress 12.14.0. It's too infrequent to demonstrate the failure consistently, only once in 20 or so runs, but I'll see if I can pin it down more.
Running: registration.cy.js (3 of 3)
There was an error reconnecting to the Chrome DevTools protocol. Please restart the browser.
TypeError: Cannot read properties of undefined (reading 'webSocketDebuggerUrl')
at _._fetchDebuggerURL (<embedded>:2404:524567)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
at async _._start (<embedded>:2404:523866)
Last command failed
Running website link test
Last command succeeded
Build step 'Execute shell' marked build as failure
Finished: FAILURE
@Pipul-Pant @awallat @alfaproject @colin0117 please take a look at this https://github.com/cypress-io/cypress/issues/26900 issue related to this one, they provided a test binary you can use to see if the possible fix is working.
Current behavior
When running the tests in Jenkins CI, using 5 VM machines in parallel there are instances that it cannot report the run result because of the
CDP_COULD_NOT_RECONNECT
error and it cannot report the result of the spec that is affected by this error.Desired behavior
Should be able to report the result of the spec that is affected by the error
CDP_COULD_NOT_RECONNECT
Test code to reproduce
This only occurs in our private project repo but I have provided cypress debug logs and masked sensitive information.
Cypress Version
12.12.0
Node version
14.6.0
Operating System
linux Debian - 10.8
Debug Logs