-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Increase await timeout for testCancelFailedSearchWhenPartialResultDisallowed #123084
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
Conversation
|
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
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.
|
@JVerwolf There are different failures on that test, so while it's not the cause, it seems to cause some secondary failures. Not sure it it's worth fixing or fixing the main cause would also fix this... |
JVerwolf
left a comment
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.
Thanks for the context @smalyshev. Ok, I'll approve this then.
WDYT about this issue marked as fixing #121719 - this isn't quite true, right?
|
No, it's totally not true, I meant it as reference, and wrote "fixes" out of habit, it shouldn't actually close that issue. |
💔 Backport failed
You can use sqren/backport to manually backport by running |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
|
The same failure still happened with the change here. See https://gradle-enterprise.elastic.co/s/oau6o5i3yjwua |
Kinda hard to figure out why it may fail but my one assumption is the search doesn't start for too long so by the time it arrives to latch unlock, it's too late, because assertBusy is 30s, but latch is just 10s.
See: #121719