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 CI] Intermittent failures with Cypress #1599

Closed
DarshitChanpura opened this issue Oct 3, 2023 · 3 comments
Closed

[Flaky CI] Intermittent failures with Cypress #1599

DarshitChanpura opened this issue Oct 3, 2023 · 3 comments
Assignees
Labels

Comments

@DarshitChanpura
Copy link
Member

In recent CI runs, there were flaky failures observed which went away on subsequent retries. Here is the failure log:

Cypress failed to make a connection to Firefox.

This usually indicates there was a problem opening the Firefox browser.

Error: could not find CRI target
    at lazyAssLogic (/home/runner/.cache/Cypress/9.5.4/Cypress/resources/app/node_modules/lazy-ass/index.js:110:14)
    at lazyAss (/home/runner/.cache/Cypress/9.5.4/Cypress/resources/app/node_modules/lazy-ass/index.js:115:28)
    at findStartPage (/home/runner/.cache/Cypress/9.5.4/Cypress/resources/app/packages/server/lib/browsers/protocol.js:56:28)
    at runMicrotasks (<anonymous>:null:null)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

error Command failed with exit code 1.

And here is a recent build output: https://github.com/opensearch-project/security-dashboards-plugin/actions/runs/6395013515/job/17357702336?pr=1580

Expected outcome:

  1. Analyze whether this is a bug on our end or from cypress side.
  2. Implement a fix.
@DarshitChanpura
Copy link
Member Author

Seems like an issue from cypress side: cypress-io/cypress#6518

@stephen-crawford
Copy link
Contributor

[Triage] Hi @DarshitChanpura, thank you for filing this issue. We can still have someone confirm this and then close. Thank you.

@cwperks
Copy link
Member

cwperks commented Jan 18, 2024

#1728 will resolve the error seen in the OP of this issue. The tests will now run with Chrome instead of FireFox.

The tests are currently only running on the ubuntu-latest runners and will need to be re-enabled on windows. The windows CI is unstable as a result of slow runners that run out of disk space after installing OSD. There is a separate issue around support for Windows so I will close this issue as the OP is resolved.

@cwperks cwperks closed this as completed Jan 18, 2024
@cwperks cwperks self-assigned this Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants