Open kibanamachine opened 1 month ago
Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)
New failure: kibana-on-merge - 8.x
New failure: kibana-on-merge - main
New failure: kibana-on-merge - 8.x
New failure: kibana-on-merge - main
New failure: kibana-on-merge - main
New failure: kibana-on-merge - main
/skip
Skipped
main: 9bca8b744af8bf2b2b5e5ff74680c494ae7d1824 8.x: 5f86c957f270c67fa98d3f408f8f0841c9c2f1ab
New failure: kibana-on-merge - 8.x
Pinging @elastic/security-solution (Team: SecuritySolution)
Pinging @elastic/security-detections-response (Team:Detections and Resp)
@maximpn @xcrzx 👋
I assigned you to this one and https://github.com/elastic/kibana/issues/196470. By the end of this week we need to figure out who can work on these. The goal is to understand if these test failures are indications of a bug - in which case we will have less than one week for fixing it for v8.16.0
according to the release schedule.
@banderror I created https://github.com/elastic/kibana/pull/197660 to address flakiness reported in this ticket and in https://github.com/elastic/kibana/issues/196470. It seems we might have race condition when performing bulk operations on enabled rules picked up by the task manager at the same time. I left only two functional tests with enabled rules since these tests check rule disabling. After applying my changes don't see any flakiness.
New failure: kibana-on-merge - 8.16
New failure: kibana-on-merge - 8.16
New failure: kibana-on-merge - 8.16
A test failed on a tracked branch
First failure: kibana-on-merge - main