Skip to content

Firefox system-tests still flake after proxy correlation updates #31482

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

Open
AtofStryker opened this issue Apr 10, 2025 · 1 comment · May be fixed by #31651
Open

Firefox system-tests still flake after proxy correlation updates #31482

AtofStryker opened this issue Apr 10, 2025 · 1 comment · May be fixed by #31651
Assignees
Labels
process: flaky test Related to test(s) that have flake in our internal tests type: chore Work is required w/ no deliverable to end user

Comments

@AtofStryker
Copy link
Contributor

Current behavior

There looks to be still some firefox system-test flake after #31377, in particular

Desired behavior

this test should no longer flake and prerequests should be removed and not time out

Test code to reproduce

N/A

Cypress Version

14.3.0

Node version

20.18.1

Operating System

linux

Debug Logs

Other

No response

@AtofStryker AtofStryker self-assigned this Apr 10, 2025
@AtofStryker AtofStryker changed the title Firefox system-tests still flake Firefox system-tests still flake after proxy correlation updates Apr 10, 2025
@MikeMcC399
Copy link
Contributor

@AtofStryker

@jennifer-shehane jennifer-shehane added process: flaky test Related to test(s) that have flake in our internal tests type: chore Work is required w/ no deliverable to end user labels Apr 11, 2025
@AtofStryker AtofStryker linked a pull request May 6, 2025 that will close this issue
3 tasks
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 type: chore Work is required w/ no deliverable to end user
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants