-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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] LangPainlessClientYamlTestSuiteIT test {yaml=painless/146_dense_vector_bit_basic/Cosine Similarity is not supported} failing #110290
Comments
…t {yaml=painless/146_dense_vector_bit_basic/Cosine Similarity is not supported} #110290
This has been muted on branch main Mute Reasons:
Build Scans: |
Pinging @elastic/es-core-infra (Team:Core/Infra) |
@benwtrent could this be related to #110059? |
Pinging @elastic/es-search (Team:Search) |
This happens in cases where an index has more than 1 shards, even if we get expected failures on 1 shard, no failures on other empty shards make the whole request return 200. I will fix the test to ensure that index has always 1 shard. |
Bit vector tests were failing in cases where an index has more than 1 shards. For error cases when we expected a failure of the whole request, shards with empty documents returned success and the whoel request unexpectedly returned 200. Ensuring that index contains only 1 shard fixes these failures. Closes elastic#110290, elastic#110291
Bit vector tests were failing in cases where an index has more than 1 shards. For error cases when we expected a failure of the whole request, shards with empty documents returned success and the whoel request unexpectedly returned 200. Ensuring that index contains only 1 shard fixes these failures. Closes elastic#110290, elastic#110291
Bit vector tests were failing in cases where an index has more than 1 shards. For error cases when we expected a failure of the whole request, shards with empty documents returned success and the whoel request unexpectedly returned 200. Ensuring that index contains only 1 shard fixes these failures. Closes #110290, #110291
Build Scans:
Reproduction Line:
Applicable branches:
main
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
Issue Reasons:
Note:
This issue was created using new, in-development muting automation. Please mind any issues.
The text was updated successfully, but these errors were encountered: