Flaky test: timeouts on windows

[rachelruderman]

Link to dashboard or CircleCI failure

https://app.circleci.com/pipelines/github/cypress-io/cypress/41761/workflows/958cb274-e0b3-4e6c-873f-2a60038625c7/jobs/1731172/parallel-runs/5

Link to failing test in GitHub

Here's the link to the taskInternal function in question: https://github.com/cypress-io/cypress/blob/develop/packages/frontend-shared/cypress/e2e/support/e2eSupport.ts#L456

Analysis

Digging through the logs/artifacts we see interesting hints such as:

1. A look at the logs shows repeated instances of MaxListenersExceededWarning:

(node:1252) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 dev-server:specs:changed listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)

2. A closer look at the logs shows a performance warning from NexusSlowGuard:

3. In the video, we don't see a loading spinner between this test and the previous test -- it's still showing the previous test. From our own log in the reporter we see "no commands were issued in this test". Perhaps teardown not working as expected?

Cypress Version

10.4.0

Other

List of other timeout failures on windows with the same MaxListenersExceededWarning and NexusSlowGuard logs:

• https://app.circleci.com/pipelines/github/cypress-io/cypress/41805/workflows/c2045215-5c0b-4913-87f1-f7f78aeb6db2/jobs/1733233/tests

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