Skip to content

[CI] CoreWithMultipleProjectsClientYamlTestSuiteIT test {yaml=search.vectors/41_knn_search_bbq_hnsw/Vector rescoring has same scoring as exact search for kNN section} failing #124052

@elasticsearchmachine

Description

@elasticsearchmachine

Build Scans:

Reproduction Line:

./gradlew ":x-pack:qa:multi-project:core-rest-tests-with-multiple-projects:yamlRestTest" --tests "org.elasticsearch.multiproject.test.CoreWithMultipleProjectsClientYamlTestSuiteIT" -Dtests.method="test {yaml=search.vectors/41_knn_search_bbq_hnsw/Vector rescoring has same scoring as exact search for kNN section}" -Dtests.seed=DF1DDE5C4B469CD5 -Dtests.jvm.argline="-Des.entitlements.enabled=true" -Dtests.locale=ksf-Latn-CM -Dtests.timezone=Etc/GMT+3 -Druntime.java=21

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [search.vectors/41_knn_search_bbq_hnsw:171]: 
Expected: <3>
     but: was <2>

Issue Reasons:

  • [main] 3 failures in test test {yaml=search.vectors/41_knn_search_bbq_hnsw/Vector rescoring has same scoring as exact search for kNN section} (1.1% fail rate in 278 executions)
  • [main] 2 failures in step part-2 (1.7% fail rate in 116 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (1.7% fail rate in 118 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

Metadata

Metadata

Assignees

Labels

:Search Relevance/VectorsVector search>test-failureTriaged test failures from CITeam:Search RelevanceMeta label for the Search Relevance team in Elasticsearchlow-riskAn open issue or test failure that is a low risk to future releases

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions