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

Failing test: Security Solution Cypress.x-pack/test/security_solution_cypress/cypress/e2e/entity_analytics/hosts/host_risk_tab·cy·ts - risk tab with legacy risk score should be able to change items count per page should be able to change items count per page #174859

Closed
kibanamachine opened this issue Jan 15, 2024 · 6 comments · Fixed by #177421
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Entity Analytics Security Entity Analytics Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jan 15, 2024

A test failed on a tracked branch

AssertionError: Timed out retrying after 150000ms: Expected to find element: `[data-test-subj="loadingMoreSizeRowPopover"] button`, but never found it.
    at selectFiveItemsPerPageOption (webpack:///./tasks/host_risk.ts:44:5)
    at Context.eval (webpack:///./e2e/entity_analytics/hosts/host_risk_tab.cy.ts:62:35)

First failure: CI Build - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jan 15, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 15, 2024
@mistic mistic added the Team:Entity Analytics Security Entity Analytics Team label Jan 15, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-entity-analytics (Team:Entity Analytics)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 15, 2024
@machadoum machadoum self-assigned this Jan 16, 2024
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

machadoum added a commit that referenced this issue Jan 17, 2024
## Summary

Skip flaky tests that were unskipped because they are still failing.

Failures:       
#174860
#174859
@MindyRS MindyRS added the Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. label Jan 17, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@mistic
Copy link
Member

mistic commented Jan 18, 2024

Skipped.

main: e4a0650

@machadoum
Copy link
Member

It was already skipped here: #174990
@mistic Did the error happen again? Why did you skip the entire test switch?

CoenWarmer pushed a commit to CoenWarmer/kibana that referenced this issue Feb 15, 2024
## Summary

Skip flaky tests that were unskipped because they are still failing.

Failures:       
elastic#174860
elastic#174859
CoenWarmer pushed a commit to CoenWarmer/kibana that referenced this issue Feb 15, 2024
@hop-dev hop-dev self-assigned this Feb 21, 2024
hop-dev added a commit that referenced this issue Mar 14, 2024
### Summary
Closes #174860
Closes #174859

Hopefully fix some flaky tests for good.

Flaky test run 1 (50 ESS):
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5268
✅

Flaky test run 2 (100 ESS 100 Serverless)
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5278
✅

Flaky test run 3 100 again
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5436
✅ (ran as a lot of time has passed)

---------

Co-authored-by: kibanamachine <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Entity Analytics Security Entity Analytics Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants