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: Timeline Integration Tests - ESS Env - Basic License.x-pack/test/security_solution_api_integration/test_suites/investigation/timeline/tests/timeline_details·ts - @ess @serverless SecuritySolution Timeline @skipInServerless Timeline Details Make sure that we get kpi data #199368

Closed
kibanamachine opened this issue Nov 7, 2024 · 4 comments
Labels
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 Nov 7, 2024

A test failed on a tracked branch

Error: retry.try reached timeout 120000 ms
Error: expected 200 "OK", got 400 "Bad Request"
    at block (search.ts:77:10)
    at runAttempt (retry_for_success.ts:30:21)
    at retryForSuccess (retry_for_success.ts:99:27)
    at RetryService.try (retry.ts:52:12)
    at SearchService.send (search.ts:71:20)
    at Context.<anonymous> (timeline_details.ts:65:9)
    at Object.apply (wrap_function.js:74:16)
----
    at Test._assertStatus (node_modules/supertest/lib/test.js:252:14)
    at /opt/buildkite-agent/builds/bk-agent-prod-gcp-1731003416802696938/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:899:3)
    at fn (node_modules/superagent/src/node/index.js:1165:18)
    at IncomingMessage.<anonymous> (node_modules/superagent/src/node/parsers/json.js:19:7)
    at IncomingMessage.emit (node:events:531:35)
    at endReadableNT (node:internal/streams/readable:1696:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at onFailure (retry_for_success.ts:18:9)
    at retryForSuccess (retry_for_success.ts:85:7)
    at RetryService.try (retry.ts:52:12)
    at SearchService.send (search.ts:71:20)
    at Context.<anonymous> (timeline_details.ts:65:9)
    at Object.apply (wrap_function.js:74:16)

First failure: kibana-on-merge - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Nov 7, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 7, 2024
@kibanamachine kibanamachine added the Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. label Nov 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 Nov 7, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@PhilippeOberti
Copy link
Contributor

investigated and there is something weird happening. When running locally I saw another test failing once, not this one. I ran all the tests many many times again and no failure happened. I'm suspecting something related to login as the error I saw for the one test that failed that one time was mentioning failing with authz. The test retried many times during 120 seconds to then fail.

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

3 participants