Flaky test: Too long with no output (exceeded 10m0s): context deadline exceeded

[rachelruderman]

Link to dashboard or CircleCI failure

• https://app.circleci.com/pipelines/github/cypress-io/cypress/41757/workflows/edf97bff-eef3-4f3f-8057-4277aef7d046/jobs/1730766
• https://app.circleci.com/pipelines/github/cypress-io/cypress/42240/workflows/b213eedd-524b-4ef3-9170-b15bfc01d1c7/jobs/1753458

Link to failing test in GitHub

https://github.com/cypress-io/cypress/blob/develop/packages/driver/cypress/e2e/commands/navigation.cy.js#L495

Analysis

Tests hang during execution of navigation.cy.js file

We also see this same error as seen in #23326

$ node ../../scripts/cypress run --config experimentalSessionAndOrigin=true,experimentalModifyObstructiveThirdPartyCode=true --record --parallel --group 5x-driver-chrome:beta-experimentalSessionAndOrigin --browser chrome:beta
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[2032:0811/220636.124358:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

Cypress Version

10.4.0

Other

Search for this issue number in the codebase to find the test(s) skipped until this issue is fixed

[audriusnavickasDB]

Might be related to #21110 Also there are many more issues registered regarding Cypress hanging in CI.

[cypress-app-bot]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

[cypress-app-bot]

This issue has been closed due to inactivity.

[josekim]

I ran into this problem, "Too long with no output (exceeded 10m0s): context deadline exceeded" in circleci.

I found that the best solution around this was just to log something to the Command line using cy.task in my test. There is some setup involved, but you can see it here.

I think this may be a better solution than dealing with CircleCi Configs.
I had a test that takes about 20 minutes to complete, mainly because i'm waiting for some data to propagate through the backend before I check. I broke up my 15 minute wait time and just logged a couple of things to the command line and that fixed my problem