Skip to content
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] CcsCommonYamlTestSuiteIT test {p0=search.vectors/42_knn_search_int4_flat/Vector similarity with filter only} failing #119197

Open
elasticsearchmachine opened this issue Dec 21, 2024 · 3 comments
Assignees
Labels
low-risk An open issue or test failure that is a low risk to future releases :Search Relevance/Search Catch all for Search Relevance Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ":qa:ccs-common-rest:yamlRestTest" --tests "org.elasticsearch.test.rest.yaml.CcsCommonYamlTestSuiteIT" -Dtests.method="test {p0=search.vectors/42_knn_search_int4_flat/Vector similarity with filter only}" -Dtests.seed=D9203CD3FBF0E7A -Dtests.locale=to -Dtests.timezone=Asia/Bishkek -Druntime.java=17

Applicable branches:
8.17

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [search.vectors/42_knn_search_int4_flat:220]: field [hits.hits] doesn't have length [1]
Expected: <1>
     but: was <0>

Issue Reasons:

  • [8.17] 2 failures in test test {p0=search.vectors/42_knn_search_int4_flat/Vector similarity with filter only} (0.3% fail rate in 663 executions)
  • [8.17] 2 failures in pipeline elasticsearch-periodic (9.5% fail rate in 21 executions)

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

@elasticsearchmachine elasticsearchmachine added :Core/Infra/Core Core issues without another label >test-failure Triaged test failures from CI Team:Core/Infra Meta label for core/infra team labels Dec 21, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-core-infra (Team:Core/Infra)

@elasticsearchmachine elasticsearchmachine added the needs:risk Requires assignment of a risk label (low, medium, blocker) label Dec 21, 2024
@rjernst rjernst added :Search Relevance/Search Catch all for Search Relevance and removed :Core/Infra/Core Core issues without another label labels Jan 7, 2025
@elasticsearchmachine elasticsearchmachine added Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch and removed Team:Core/Infra Meta label for core/infra team labels Jan 7, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-search-relevance (Team:Search Relevance)

@benwtrent benwtrent added low-risk An open issue or test failure that is a low risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jan 7, 2025
@benwtrent
Copy link
Member

Like other ccs vector search failures, this is a data setup issue. Generally, this occurs when there is only one vector quantized in a given segment, which we try to protect against, but in CCS, it could be that a shard only gets a single vector.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low-risk An open issue or test failure that is a low risk to future releases :Search Relevance/Search Catch all for Search Relevance Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

4 participants