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: X-Pack Detection Engine API Integration Tests.x-pack/test/detection_engine_api_integration/security_and_spaces/group10/risk_engine/telemetry_usage·ts - detection engine api security and spaces enabled - Group 10 Risk engine telemetry Risk engine enabled "before each" hook for "should return riskEngineMetrics with expected values" #168429

Closed
kibanamachine opened this issue Oct 10, 2023 · 21 comments
Closed

Failing test: X-Pack Detection Engine API Integration Tests.x-pack/test/detection_engine_api_integration/security_and_spaces/group10/risk_engine/telemetry_usage·ts - detection engine api security and spaces enabled - Group 10 Risk engine telemetry Risk engine enabled "before each" hook for "should return riskEngineMetrics with expected values" #168429

kibanamachine opened this issue Oct 10, 2023 · 21 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Detection Engine Security Solution Detection Engine Area

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Oct 10, 2023 •
edited
Loading

A test failed on a tracked branch

Error: expected 200 "OK", got 400 "Bad Request"
    at Object.init (utils.ts:454:8)
    at Context.<anonymous> (telemetry_usage.ts:101:32)
    at Object.apply (wrap_function.js:73:16)
----
    at Test._assertStatus (node_modules/supertest/lib/test.js:252:14)
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-f620d7bd2fd18631/elastic/kibana-on-merge/kibana/node_modules/supertest/lib/test.js:308:13
    at Test._assertFunction (node_modules/supertest/lib/test.js:285:13)
    at Test.assert (node_modules/supertest/lib/test.js:164:23)
    at localAssert (node_modules/supertest/lib/test.js:120:14)
    at fn (node_modules/supertest/lib/test.js:125:7)
    at Test.callback (node_modules/superagent/src/node/index.js:925:3)
    at fn (node_modules/superagent/src/node/index.js:1166:18)
    at IncomingMessage.<anonymous> (node_modules/superagent/src/node/parsers/json.js:19:7)
    at IncomingMessage.emit (node:events:526:35)
    at endReadableNT (node:internal/streams/readable:1359:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Oct 10, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Oct 10, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@delanni
Copy link
Contributor

delanni commented Oct 10, 2023

It seems that the tests are failing because there's some improper cleaning happening?

[00:23:20]             │ proc [kibana] 		illegal_state_exception: index, alias, and data stream names need to be unique, but the following duplicates were found [data stream [risk-score.risk-score-default] conflicts with index]
[00:23:20]             └- ✖ fail: detection engine api security and spaces enabled - Group 10 Risk engine telemetry Risk engine enabled "before each" hook for "should return riskEngineMetrics with expected values"

For now, I'll disable this suite completely, because the error is in the beforeAll code, and it's failing a lot as it is.

cc: @nkhristinin

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

delanni added a commit that referenced this issue Oct 10, 2023
@delanni
chore: disable test suite (#168429)
142d1bd
@delanni delanni mentioned this issue Oct 10, 2023
Merged
delanni added a commit that referenced this issue Oct 10, 2023
@delanni
[Ops] Disable test suite (#168455)
631c62b 
## Summary
Disabling a very unstable suite
(#168429)

cc: @nkhristinin
@nkhristinin
Copy link
Contributor

Will look into this, thanks!

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@mistic
Copy link
Member

mistic commented Oct 10, 2023 •
edited
Loading

Skipped.

main: 631c62b
8.11: 5462304

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.11

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.11

mistic pushed a commit that referenced this issue Oct 12, 2023
@delanni @mistic
[Ops] Disable test suite (#168455)
5462304 
## Summary
Disabling a very unstable suite
(#168429)

cc: @nkhristinin
@mistic mistic added the v8.11.1 label Oct 12, 2023
@mistic mistic added the Team:Detection Engine Security Solution Detection Engine Area label Oct 12, 2023
@botelastic botelastic bot removed the needs-team Issues missing a team label label Oct 12, 2023
@rylnd
Copy link
Contributor

rylnd commented Oct 13, 2023

This should be closed by the work done in #168469 . Accompanying flaky test runner results can be found here.

@rylnd rylnd closed this as completed Oct 13, 2023
dej611 pushed a commit to dej611/kibana that referenced this issue Oct 17, 2023
@delanni @dej611
[Ops] Disable test suite (elastic#168455)
4c0727e 
## Summary
Disabling a very unstable suite
(elastic#168429)

cc: @nkhristinin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Detection Engine Security Solution Detection Engine Area
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@rylnd @mistic @delanni @nkhristinin @kibanamachine