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.

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: Jest Integration Tests.x-pack/plugins/security_solution/server/integration_tests - telemetry tasks sender configuration should use new sender when configured #187720

Closed
kibanamachine opened this issue Jul 7, 2024 · 7 comments
Assignees
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

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:215: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 - 8.15

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@mistic
Copy link
Member

mistic commented Jul 25, 2024

Skipped.

main: da6f7b2
8.15: 1534622

mistic added a commit that referenced this issue Jul 25, 2024
@mistic mistic added the v8.15.0 label Jul 25, 2024
@rayafratkina
Copy link
Contributor

@mchopda is anyone looking into this?

@andrewkroh
Copy link
Member

I'm not familiar with this part of the code, but it looks like an area that Security Data Analytics would be familiar with.

@donaherc, could your team help investigate this failure please?

@szaffarano szaffarano self-assigned this Oct 1, 2024
@szaffarano
Copy link
Contributor

@rayafratkina @andrewkroh
Apologies for not getting back to you sooner. I think this is related to #188234 #187719 and #178918 which are already fixed.
Since we merged the linked PR, I haven't seen this or any other integration test fail in this suite, so I'd say the flakiness is gone; hence, we could close this ticket. Do you agree?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

6 participants