-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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: X-Pack Detection Engine API Integration Tests.x-pack/test/detection_engine_api_integration/security_and_spaces/rule_execution_logic/threat_match·ts - detection engine api security and spaces enabled - rule execution logic Threat match type rules terms and match should have the same alerts with pagination #155304
Comments
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 #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. |
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 |
Skipped. main: 39dad65 |
## Unskip IM rule tests It's a tricky test fail, which not reproduces locally, also in the [PR] CI can be green(#156489) but eventually [can failed on main](#155304) In this attempt, I change the test to narrow amount of alerts for a rule which has 2 potential benefits: 1. if there is a resources problem this rule will execute faster 2. We can read the error message if it fails on the maiт. --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Unskipped here #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
The text was updated successfully, but these errors were encountered: