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: Chrome UI Functional Tests.test/functional/apps/discover/group3/_request_counts·ts - discover/group3 discover request counts ES|QL mode should send no more than 2 search requests (documents + chart) on page load #205344

Closed
kibanamachine opened this issue Jan 2, 2025 · 7 comments · Fixed by #205690
Closed

Failing test: Chrome UI Functional Tests.test/functional/apps/discover/group3/_request_counts·ts - discover/group3 discover request counts ES|QL mode should send no more than 2 search requests (documents + chart) on page load #205344

kibanamachine opened this issue Jan 2, 2025 · 7 comments · Fixed by #205690
Assignees
@kertal
Labels
failed-es-promotion failed-test A test failure on a tracked branch, potentially flaky-test impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:small Small Level of Effort Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jan 2, 2025 •
edited
Loading

A test failed on a tracked branch

Error: retry.try reached timeout 120000 ms
Error: expected 4 to equal 3
    at Assertion.assert (expect.js:100:11)
    at Assertion.apply (expect.js:227:8)
    at Assertion.be (expect.js:69:22)
    at _request_counts.ts:78:26
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at runAttempt (retry_for_success.ts:30:15)
    at retryForSuccess (retry_for_success.ts:99:21)
    at RetryService.try (retry.ts:52:12)
    at expectSearchCount (_request_counts.ts:56:7)
    at Context.<anonymous> (_request_counts.ts:120:9)
    at Object.apply (wrap_function.js:74:16)
    at onFailure (retry_for_success.ts:18:9)
    at retryForSuccess (retry_for_success.ts:85:7)
    at RetryService.try (retry.ts:52:12)
    at expectSearchCount (_request_counts.ts:56:7)
    at Context.<anonymous> (_request_counts.ts:120:9)
    at Object.apply (wrap_function.js:74:16)

First failure: kibana-elasticsearch-snapshot-verify - 8.x
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jan 2, 2025
@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 2, 2025
@kibanamachine kibanamachine added failed-es-promotion Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. labels Jan 2, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 2, 2025
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@davismcphee davismcphee added loe:small Small Level of Effort impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Jan 3, 2025
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@jbudz
Copy link
Member

jbudz commented Jan 3, 2025

/skip

kibanamachine added a commit that referenced this issue Jan 3, 2025
@kibanamachine
skip failing test suite (#205344)
2c7c1c7
@kibanamachine
Copy link
Contributor Author

Skipped

8.x: 2c7c1c7
main: ff6adff

kibanamachine added a commit that referenced this issue Jan 3, 2025
@kibanamachine
skip failing test suite (#205344)
ff6adff
@davismcphee davismcphee added impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. and removed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Jan 6, 2025
@davismcphee
Copy link
Contributor

@kertal Unfortunately it looks like we're experiencing some flakiness with the ES|QL tests 😔

@kertal kertal mentioned this issue Jan 7, 2025
Merged
1 task
@kertal
Copy link
Member

kertal commented Jan 7, 2025

@davismcphee yes, and those are pretty hard to resolve. I'd suggest to unskip the main test, and just skip the ES|QL part for now, aiming to stabilize those later on #205690

kowalczyk-krzysztof pushed a commit to kowalczyk-krzysztof/kibana that referenced this issue Jan 7, 2025
@kibanamachine @kowalczyk-krzysztof
skip failing test suite (elastic#205344)
505d012
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Jan 13, 2025
@kibanamachine @CAWilson94
skip failing test suite (elastic#205344)
6f89a48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kertal kertal

Labels
failed-es-promotion failed-test A test failure on a tracked branch, potentially flaky-test impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:small Small Level of Effort Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Discover] Unskip functional discover request counts test and skip ES|QL part kertal/kibana
5 participants
@kertal @jbudz @elasticmachine @davismcphee @kibanamachine