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.

Sign up for GitHub

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

Jump to bottom

Failing test: Security Solution Cypress.x-pack/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/prebuilt_rules/management·cy·ts - Prebuilt rules Alerts rules, prebuilt rules "before each" hook for "Loads prebuilt rules" "before each" hook for "Loads prebuilt rules" #182442

Open
Tracked by #182682
kibanamachine opened this issue May 2, 2024 · 23 comments
Open
Tracked by #182682

Failing test: Security Solution Cypress.x-pack/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/prebuilt_rules/management·cy·ts - Prebuilt rules Alerts rules, prebuilt rules "before each" hook for "Loads prebuilt rules" "before each" hook for "Loads prebuilt rules" #182442

kibanamachine opened this issue May 2, 2024 · 23 comments
Assignees
@banderror
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area skipped-test Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented May 2, 2024 •
edited
Loading

A test failed on a tracked branch

AssertionError: Timed out retrying after 150000ms: Expected to find element: `[data-test-subj="rules-management-table"]`, but never found it.

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `Prebuilt rules`
    at waitForPrebuiltDetectionRulesToBeLoaded (webpack:///./tasks/alerts_detection_rules.ts:271:33)
    at Context.eval (webpack:///./e2e/detection_response/rule_management/prebuilt_rules/management.cy.ts:63:44)

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label May 2, 2024
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@botelastic botelastic bot added the needs-team Issues missing a team label label May 2, 2024
@kibanamachine kibanamachine added the Team:Detection Rule Management Security Detection Rule Management Team label May 2, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

@botelastic botelastic bot removed the needs-team Issues missing a team label label May 2, 2024
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@banderror
Copy link
Contributor

/skip

kibanamachine added a commit that referenced this issue May 2, 2024
@kibanamachine
skip failing test suite (#182442)
4b9f1bc
@kibanamachine
Copy link
Contributor Author

Skipped

main: 4b9f1bc

@banderror
Copy link
Contributor

Looks like it was broken by #181616 and fixed by #182432. We can unskip the test now 😄

@banderror banderror mentioned this issue May 2, 2024
Closed
@banderror banderror added Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area 8.15 candidate labels May 2, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

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

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@banderror banderror self-assigned this May 2, 2024
@banderror banderror mentioned this issue May 6, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@banderror banderror

Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area skipped-test Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@banderror @elasticmachine @kibanamachine