Skip to content

[CI] Ec2DiscoveryTests testFilterByMultipleTags failing #125166

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 Mar 18, 2025 · 3 comments · Fixed by #125109
Closed

[CI] Ec2DiscoveryTests testFilterByMultipleTags failing #125166

elasticsearchmachine opened this issue Mar 18, 2025 · 3 comments · Fixed by #125109
Labels
:Distributed Coordination/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure low-risk An open issue or test failure that is a low risk to future releases Team:Distributed Coordination Meta label for Distributed Coordination team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Mar 18, 2025 •
edited
Loading

Build Scans:

Reproduction Line:

./gradlew ":plugins:discovery-ec2:test" --tests "org.elasticsearch.discovery.ec2.Ec2DiscoveryTests.testFilterByMultipleTags" -Dtests.seed=14E31C1D1F072933 -Dtests.locale=dz -Dtests.timezone=Asia/Karachi -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: a collection with size <2>
     but: collection size was <0>

Issue Reasons:

  • [main] 3 consecutive failures in step part1
  • [main] 3 consecutive failures in pipeline elasticsearch-intake
  • [main] 12 failures in test testFilterByMultipleTags (5.2% fail rate in 233 executions)
  • [main] 6 failures in step part-1 (5.7% fail rate in 106 executions)
  • [main] 5 failures in step part1 (15.2% fail rate in 33 executions)
  • [main] 6 failures in pipeline elasticsearch-pull-request (5.8% fail rate in 104 executions)
  • [main] 5 failures in pipeline elasticsearch-intake (15.2% fail rate in 33 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Distributed Coordination/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure >test-failure Triaged test failures from CI labels Mar 18, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.x

Mute Reasons:

  • [8.x] 3 failures in test testFilterByMultipleTags (2.1% fail rate in 143 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Mar 18, 2025
@elasticsearchmachine
Mute org.elasticsearch.discovery.ec2.Ec2DiscoveryTests testFilterByMu…
7cffc50 
…ltipleTags #125166
@elasticsearchmachine elasticsearchmachine added needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Distributed Coordination Meta label for Distributed Coordination team labels Mar 18, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination)

@nicktindall
Copy link
Contributor

Also seemingly caused by aws/aws-sdk-java-v2#5968 (I checked one break and it was locale=sd...

@nicktindall nicktindall mentioned this issue Mar 18, 2025
Merged
@nicktindall nicktindall 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 Mar 18, 2025
DaveCTurner added a commit that referenced this issue Mar 19, 2025
@DaveCTurner
Work around testFilterByTags failure (#125109)
1b22b0e 
A SDK bug[^1] means that these values sometimes don't parse as an
integer. We don't need them to do so in order to pass the test, so this
commit relaxes the test to accept any string.

Closes #125090 Closes #125166

[^1]: aws/aws-sdk-java-v2#5968
smalyshev pushed a commit to smalyshev/elasticsearch that referenced this issue Mar 21, 2025
@DaveCTurner @smalyshev
Work around testFilterByTags failure (elastic#125109)
8c4d9d1 
A SDK bug[^1] means that these values sometimes don't parse as an
integer. We don't need them to do so in order to pass the test, so this
commit relaxes the test to accept any string.

Closes elastic#125090 Closes elastic#125166

[^1]: aws/aws-sdk-java-v2#5968
omricohenn pushed a commit to omricohenn/elasticsearch that referenced this issue Mar 28, 2025
@DaveCTurner @omricohenn
Work around testFilterByTags failure (elastic#125109)
b534a10 
A SDK bug[^1] means that these values sometimes don't parse as an
integer. We don't need them to do so in order to pass the test, so this
commit relaxes the test to accept any string.

Closes elastic#125090 Closes elastic#125166

[^1]: aws/aws-sdk-java-v2#5968
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Distributed Coordination/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure low-risk An open issue or test failure that is a low risk to future releases Team:Distributed Coordination Meta label for Distributed Coordination team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Work around testFilterByTags failure DaveCTurner/elasticsearch
2 participants
@nicktindall @elasticsearchmachine