Skip to content

[CI] DenseVectorFieldMapperTests testRescoreVectorOldIndexVersion failing #127657

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.

Sign up for GitHub

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

Jump to bottom
Closed
elasticsearchmachine opened this issue May 2, 2025 · 2 comments · Fixed by #127659
Closed

[CI] DenseVectorFieldMapperTests testRescoreVectorOldIndexVersion failing #127657

elasticsearchmachine opened this issue May 2, 2025 · 2 comments · Fixed by #127659
Assignees
@benwtrent
Labels
needs:risk Requires assignment of a risk label (low, medium, blocker) :Search Relevance/Vectors Vector search 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 ":server:test" --tests "org.elasticsearch.index.mapper.vectors.DenseVectorFieldMapperTests.testRescoreVectorOldIndexVersion" -Dtests.seed=259C644E7360502E -Dtests.locale=sg-Latn-CF -Dtests.timezone=Etc/Zulu -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

junit.framework.AssertionFailedError: Expected exception MapperParsingException but no exception was thrown

Issue Reasons:

  • [main] 2 consecutive failures in step part1
  • [main] 2 consecutive failures in pipeline elasticsearch-intake
  • [main] 3 failures in test testRescoreVectorOldIndexVersion (1.7% fail rate in 180 executions)
  • [main] 2 failures in step part1 (14.3% fail rate in 14 executions)
  • [main] 2 failures in pipeline elasticsearch-intake (14.3% fail rate in 14 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Search Relevance/Vectors Vector search >test-failure Triaged test failures from CI labels May 2, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 consecutive failures in step part1
  • [main] 2 consecutive failures in pipeline elasticsearch-intake
  • [main] 3 failures in test testRescoreVectorOldIndexVersion (1.7% fail rate in 180 executions)
  • [main] 2 failures in step part1 (14.3% fail rate in 14 executions)
  • [main] 2 failures in pipeline elasticsearch-intake (14.3% fail rate in 14 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch labels May 2, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

pull bot pushed a commit to Zezo-Ai/elasticsearch that referenced this issue May 2, 2025
@elasticsearchmachine
Mute org.elasticsearch.index.mapper.vectors.DenseVectorFieldMapperTes…
9801d45 
…ts testRescoreVectorOldIndexVersion elastic#127657
@benwtrent benwtrent self-assigned this May 2, 2025
benwtrent added a commit to benwtrent/elasticsearch that referenced this issue May 2, 2025
@benwtrent
Fixing test failure elastic#127657
944c5cc
@benwtrent benwtrent mentioned this issue May 2, 2025
Merged
benwtrent added a commit that referenced this issue May 5, 2025
@benwtrent
Fixing test failure #127657 (#127659)
ba37435
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@benwtrent benwtrent

Labels
needs:risk Requires assignment of a risk label (low, medium, blocker) :Search Relevance/Vectors Vector search Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixing test failure #127657 benwtrent/elasticsearch
2 participants
@benwtrent @elasticsearchmachine