Fix flakiness on YAML tests for Sparse Vector #137202
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
markjhoy
added
>non-issue
>test
elasticsearchmachine
added
the
needs:triage
kderusso
approved these changes
Oct 27, 2025
Member
kderusso
left a comment
kderusso
left a comment
There was a problem hiding this comment.
I realize that we can't repro this locally but we should probably unmute the tests if we think this is the fix.
Contributor
Author
Ah - good idea - where can this be found? I can't seem to find it :/ |
Member
|
@markjhoy Muted tests are in muted-tests.yml - you can remove the 3 lines for each applicable muted test. |
markjhoy
added
the
:SearchOrg/Relevance
elasticsearchmachine
added
Team:Search - Relevance
Collaborator
|
Pinging @elastic/search-relevance (Team:Search - Relevance) |
Collaborator
💔 Backport failed
You can use sqren/backport to manually backport by running |
markjhoy
added a commit
to markjhoy/elasticsearch
that referenced
this pull request
Oct 28, 2025
* add indices to deletion on teardown * unmute test (only the 1 is muted) (cherry picked from commit 2d45a8d) # Conflicts: # muted-tests.yml
markjhoy
added a commit
to markjhoy/elasticsearch
that referenced
this pull request
Oct 28, 2025
* add indices to deletion on teardown * unmute test (only the 1 is muted) (cherry picked from commit 2d45a8d) # Conflicts: # muted-tests.yml
markjhoy
added a commit
to markjhoy/elasticsearch
that referenced
this pull request
Oct 28, 2025
* add indices to deletion on teardown * unmute test (only the 1 is muted) (cherry picked from commit 2d45a8d) # Conflicts: # muted-tests.yml
Contributor
Author
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
markjhoy
added a commit
that referenced
this pull request
Oct 28, 2025
markjhoy
added a commit
that referenced
this pull request
Oct 28, 2025
markjhoy
added a commit
that referenced
this pull request
Oct 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Two of the
sparse_vectorintegration tests are sporadically failing due to extra results in the output. This PR attempts to fix that by ensuring those test indices are deleted and the index metadata is refreshed.The two tests (in x-pack) are:
ml/sparse_vector_search/Check sparse_vector should prune by defaultml/sparse_vector_search/Test sparse_vector search with query vector and pruning config