-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Fix flaky bsearch test #99277
Fix flaky bsearch test #99277
Conversation
Pinging @elastic/kibana-app-services (Team:AppServices) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is one more place we check:
kibana/test/api_integration/apis/search/bsearch.ts
Lines 86 to 87 in 9762065
expect(responseJson.result.isPartial).to.be(false); | |
expect(responseJson.result.isRunning).to.be(false); |
Should we update that also?
btw, here is the failure: #98098
Also curious if we'd rather added logic to refetch until completed (similar to our polling inside Kibana), but I think this is not for this pr.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just see: #99277 (review)
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @lukasolson |
* Fix flaky bsearch test * Review feedback
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
* Fix flaky bsearch test * Review feedback Co-authored-by: Lukas Olson <[email protected]>
Summary
Fixes #98245.
As @Dosant pointed out in #98245 (comment), this test started being flaky when we switched the default to async search, since it can possibly return partial responses. This PR updates the test to check that the property exists rather than checking the value itself.
Checklist
For maintainers