Open kibanamachine opened 3 weeks ago
Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)
Pinging @elastic/security-solution (Team: SecuritySolution)
Pinging @elastic/security-detections-response (Team:Detections and Resp)
This test failure and https://github.com/elastic/kibana/issues/190952 are failures of the same test get_prebuilt_rules_status should return empty structure when no prebuilt rule assets
in two different builds and in both ESS and Serverless.
Both test runs were retried and succeeded, but nonetheless it strongly feels as flakiness of the test itself. The test expects to have 0 prebuilt rule assets in the index but there are clearly some of them, which might indicate an issue with test isolation.
I'll skip the test if it continues to fail and our team will work on fixing it next week.
New failure: kibana-on-merge - main
@banderror - we're getting anomaly warnings about this failing on several PR builds also, so it's confirmed to be flaky. I suggest skipping this as it may well be blocking devs
New failure: kibana-on-merge - main
New failure: kibana-on-merge - main
/skip
Skipped
main: c4a39e1291dc3c8e23db0104a8270c0b39324fd1
@delanni Yes, now it's clear that it's a flaky test. Thanks for skipping.
A test failed on a tracked branch
First failure: kibana-on-merge - main