Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flaky test: AssertionError: Timed out retrying after 4000ms: Expected to find content: '/(a few|[0-9]) seconds? ago/' within the element: <div.h-full.grid.grid-col-1.git-info-row.justify-start.items-center> but never did. #23474

Closed
rachelruderman opened this issue Aug 19, 2022 · 6 comments
Labels
process: flaky test Related to test(s) that have flake in our internal tests stale no activity on this issue for a long period

Comments

@rachelruderman
Copy link
Contributor

rachelruderman commented Aug 19, 2022

Link to dashboard or CircleCI failure

https://app.circleci.com/pipelines/github/cypress-io/cypress/42258/workflows/bec5f1bd-84fa-46cd-95ad-e7061cdc20e3/jobs/1754508

Link to failing test in GitHub

https://github.com/cypress-io/cypress/blob/develop/packages/app/cypress/e2e/specs_list_no_git_repo.cy.ts#L9

Analysis

Screen Shot 2022-08-19 at 2 30 20 PM

Cypress Version

10.5.0

Other

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

@marktnoonan
Copy link
Contributor

Just a note for future folks who might pick this up. I bumped into this skipped test and was curious about the flake, I ran it 20 times on my mac just now and it passed every time. Since the failure linked is on Windows, I'm going to guess this is flaky due to specific issues running Cypress on Windows (maybe just speed) and would need to be reproduced there to fix.

@flotwig flotwig added the process: flaky test Related to test(s) that have flake in our internal tests label Feb 1, 2023
@flotwig
Copy link
Contributor

flotwig commented Feb 1, 2023

Since the failure linked is on Windows, I'm going to guess this is flaky due to specific issues running Cypress on Windows (maybe just speed) and would need to be reproduced there to fix.

@marktnoonan coincidentally I was just looking at this for #25671 - I ran this 100x in Windows and it passed every time. gonna try unskipping it... 🤞

@marktnoonan
Copy link
Contributor

Oh nice @flotwig. I am unskipping a bunch of things to see what is still failing, it looks like there are at least a couple tests we can turn back on, and a few that have gotten super stale and need full rewrites (eg referencing UI that doesn't exist any more).

What I'm really looking for is anything we turned off as "flaky" that is now "100% failing" which would represent a new bug.

flotwig added a commit that referenced this issue Feb 1, 2023
Couldn't get to flake: #23474 (comment)
@flotwig
Copy link
Contributor

flotwig commented Feb 2, 2023

Seems like it still fails in CI persistently, so never mind :/

@cypress-app-bot
Copy link
Collaborator

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 cypress-app-bot added the stale no activity on this issue for a long period label Aug 2, 2023
@cypress-app-bot
Copy link
Collaborator

This issue has been closed due to inactivity.

@cypress-app-bot cypress-app-bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
process: flaky test Related to test(s) that have flake in our internal tests stale no activity on this issue for a long period
Projects
None yet
Development

No branches or pull requests

4 participants