Closed kibanamachine closed 1 year ago
Pinging @elastic/security-solution (Team: SecuritySolution)
Pinging @elastic/security-detections-response (Team:Detections and Resp)
New failure: CI Build - main
/skip
New failure: CI Build - 8.8
New failure: CI Build - main
For posterity: this test was introduced to cover the changes in https://github.com/elastic/kibana/pull/144511.
As an aside: the failure message for this test is not helpful as the diff is too large to output. Perhaps it would make sense to compare these alerts in series, so that the failure shows two single objects? Just a thought.
Merged in the PR unskipping these as running them multiple times locally and on the flakey test runner did not reveal any failures.
Lets keep in mind @rylnd 's suggestion if this pops up again.
If anyone happens to have reproduced this locally and was able to actually observe full failure message, please share here! Do we think this was simply a false negative?
New failure: CI Build - main
New failure: CI Build - main
Unskipped here https://github.com/elastic/kibana/pull/160094
New failure: CI Build - main
Hey @yctercero may you please take a look at this new failure when you have the chance? Thanks!
@MadameSheema the detections team is working 8.10 to address all open flakey and skipped tests. Will add this one to the list.
There another PR which should address it
New failure: CI Build - main
Running it through flaky runner https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2625
After successfully running this test through the Flaky Test Runner for 100 iterations without any failures, it has been determined that the test is not truly flaky or failing. As a result, the ticket can be closed.
A test failed on a tracked branch
First failure: CI Build - main