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] XPackRestIT test {p0=terms_enum/10_basic/Test security} failing #116178

Open
elasticsearchmachine opened this issue Nov 4, 2024 · 4 comments
Labels
low-risk An open issue or test failure that is a low risk to future releases :Search Relevance/Ranking Scoring, rescoring, rank evaluation. 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 ":x-pack:plugin:yamlRestTest" --tests "org.elasticsearch.xpack.test.rest.XPackRestIT.test {p0=terms_enum/10_basic/Test security}" -Dtests.seed=53BDDA28E105FDDF -Dtests.locale=guz-KE -Dtests.timezone=Brazil/East -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [terms_enum/10_basic:581]: field [terms] doesn't have length [1]
Expected: <1>
     but: was <0>

Issue Reasons:

  • [main] 4 failures in test test {p0=terms_enum/10_basic/Test security} (0.6% fail rate in 709 executions)
  • [main] 2 failures in step part-3 (1.9% fail rate in 103 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (1.7% fail rate in 120 executions)

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

@elasticsearchmachine elasticsearchmachine added :Search Relevance/Ranking Scoring, rescoring, rank evaluation. >test-failure Triaged test failures from CI labels Nov 4, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 4 failures in test test {p0=terms_enum/10_basic/Test security} (0.6% fail rate in 709 executions)
  • [main] 2 failures in step part-3 (1.9% fail rate in 103 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (1.7% fail rate in 120 executions)

Build Scans:

@elasticsearchmachine
Copy link
Collaborator Author

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

@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 Nov 4, 2024
jozala pushed a commit that referenced this issue Nov 13, 2024
@benwtrent
Copy link
Member

Only one of the failures actually looks like a "valid" test failure. The rest were caused by some larger failure (ILM policy bug, ML template failing to create).

I am gonna unmute this.

The only valid test failure that I can find: https://gradle-enterprise.elastic.co/s/3oocp75hqvi34

Gonna see if this replicates or if there are any weird security terms enum commits around the time of that initial failure.

@benwtrent
Copy link
Member

The failing build's logs. Honestly, nothing stands out to me at all :(.
build.zip

benwtrent added a commit to benwtrent/elasticsearch that referenced this issue Dec 5, 2024
@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 Dec 5, 2024
elasticsearchmachine pushed a commit that referenced this issue Dec 6, 2024
There was a single valid test failure, and this failure COULD have been
caused by some of the weird race conditions introduced around that time
in DFS/query phase optimizations. 

Unmuting to see if its actually fixed

Related: #116178
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/Ranking Scoring, rescoring, rank evaluation. 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

2 participants