-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
[CI] AsyncSearchActionTests fails unpredictably #53360
Comments
Pinging @elastic/es-search (:Search/Search) |
@jimczi Thanks for handling this! |
thanks for muting @williamrandolph , I'll watch the build since I was not able to reproduce the exact same exceptions locally. |
Reopened since it failed on the first build :( |
This change removes the need to always get a new version when iterating on an async search. This is needed since we cannot guarantee that shards will be queried exactly in order. Relates #53360
There was another failure just now on master, Jenkins build and Build scan Failure details, as there's a problem with the build scan that makes it a pain to access this info:
|
Deleting an async search id can throw a ResourceNotFoundException even if the query was successfully cancelled. We delete the stored response automatically if the query is cancelled so that creates a race with the delete action that also ensures that the task is removed. This change ensures that we ignore missing async search ids in the async search index if they were successfuly cancelled. Relates elastic#53360 Relates elastic#49931
This test failed in CI and there has been an ongoing issue for tests in this class failing. Relates elastic#53360
Deleting an async search id can throw a ResourceNotFoundException even if the query was successfully cancelled. We delete the stored response automatically if the query is cancelled so that creates a race with the delete action that also ensures that the task is removed. This change ensures that we ignore missing async search ids in the async search index if they were successfully cancelled. Relates #53360 Relates #49931
Another failure of several tests today on 7.x intake: https://gradle-enterprise.elastic.co/s/ldwksp7pl32ye
|
This change removes the need to always get a new version when iterating on an async search. This is needed since we cannot guarantee that shards will be queried exactly in order. Relates #53360
Thanks @mayya-sharipova , a backport was missing, I pushed dc2edc9 and will watch the build in 7.x before closing. |
The tests seem stable in master and 7.x, hence closing. |
This started to fail for "darwin-compatibility" since March 27 for But I cannot reproduce locally:
Sample error message
Build scan: Failure email notification: |
I am closing this issue as recent discussion is in #54180 |
We've had a couple of test failures from
AsyncSearchActionTests
today. The failures haven't reproduced locally for me.Failure on
master
: https://gradle-enterprise.elastic.co/s/asvh7ted2nfvy/Earlier failure on
7.xmaster: https://gradle-enterprise.elastic.co/s/3pjzmjjxc66wiI believe @jimczi is working on this actively, but I'm going to go ahead and mute while he's in progress.
Relates #49931
The text was updated successfully, but these errors were encountered: