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: Jest Integration Tests.x-pack/plugins/security_solution/server/integration_tests - telemetry tasks detection-rules should send task metrics #187719

Closed
kibanamachine opened this issue Jul 7, 2024 · 10 comments
Closed

Failing test: Jest Integration Tests.x-pack/plugins/security_solution/server/integration_tests - telemetry tasks detection-rules should send task metrics #187719

kibanamachine opened this issue Jul 7, 2024 · 10 comments
Assignees
@szaffarano
Labels
failed-es-promotion failed-test A test failure on a tracked branch, potentially flaky-test Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jul 7, 2024 •
edited
Loading

A test failed on a tracked branch

Error: expect(received).toBeGreaterThan(expected)

Expected: > 0
Received:   0
    at Object.toBeGreaterThan (/opt/buildkite-agent/builds/bk-agent-prod-gcp-1720358802600294719/elastic/kibana-elasticsearch-serverless-verify-and-promote/kibana/x-pack/plugins/security_solution/server/integration_tests/telemetry.test.ts:171:31)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

First failure: kibana-elasticsearch-serverless-verify-and-promote - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jul 7, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Jul 7, 2024
@kibanamachine kibanamachine added failed-es-promotion Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Jul 7, 2024
@elasticmachine
Copy link
Contributor

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

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

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

mistic added a commit that referenced this issue Jul 17, 2024
@mistic
skip flaky suite (#187719)
10c7ee3
@mistic
Copy link
Member

mistic commented Jul 17, 2024

Skipped.

main: 10c7ee3

@szaffarano szaffarano self-assigned this Jul 19, 2024
@szaffarano
Copy link
Contributor

Re enabled here

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.15

@kibanamachine kibanamachine reopened this Jul 23, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

mistic added a commit that referenced this issue Jul 24, 2024
@mistic
skip flaky suites (#187719)
aa90561
mistic added a commit that referenced this issue Jul 24, 2024
@mistic
skip flaky suites (#187719)
ab27391
@mistic
Copy link
Member

mistic commented Jul 24, 2024

Skipped.

main: aa90561
8.15: ab27391

@mistic mistic added the v8.15.0 label Jul 24, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@szaffarano szaffarano mentioned this issue Aug 7, 2024
Merged
szaffarano added a commit that referenced this issue Aug 7, 2024
@szaffarano
[Telemetry][Security Solution] Fix flaky tests (#190044)
358e104 
## Summary

Fixes: #188234
#187719 and
#178918

The flakiness was while calculating the Detection Rules task
invocations. It could have two different RCs: 1) The code didn't retry
in case the task wasn't executed yet, which makes sense in a CI
environment, which is slower than a dev environment; 2) The timestamp to
filter out requests was calculated after the task was triggered, and if
the task is executed fast enough, it could lead to empty responses
because of that.
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Aug 7, 2024
@szaffarano
[Telemetry][Security Solution] Fix flaky tests (elastic#190044)
e0ca564 
## Summary

Fixes: elastic#188234
elastic#187719 and
elastic#178918

The flakiness was while calculating the Detection Rules task
invocations. It could have two different RCs: 1) The code didn't retry
in case the task wasn't executed yet, which makes sense in a CI
environment, which is slower than a dev environment; 2) The timestamp to
filter out requests was calculated after the task was triggered, and if
the task is executed fast enough, it could lead to empty responses
because of that.

(cherry picked from commit 358e104)
@szaffarano szaffarano mentioned this issue Oct 1, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@szaffarano szaffarano

Labels
failed-es-promotion failed-test A test failure on a tracked branch, potentially flaky-test Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@szaffarano @mistic @elasticmachine @kibanamachine