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.

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

[CI] Ec2DiscoveryTests testDefaultSettings failing #114089

Closed
elasticsearchmachine opened this issue Oct 4, 2024 · 1 comment · Fixed by #114101
Closed

[CI] Ec2DiscoveryTests testDefaultSettings failing #114089

elasticsearchmachine opened this issue Oct 4, 2024 · 1 comment · Fixed by #114101
Assignees
@DaveCTurner
Labels
:Distributed/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 Meta label for distributed team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ':plugins:discovery-ec2:test' --tests "org.elasticsearch.discovery.ec2.Ec2DiscoveryTests.testPublicIp" -Dtests.seed=67E5E30A1DC80CD3 -Dtests.locale=ne -Dtests.timezone=America/Virgin -Druntime.java=23

Applicable branches:
7.17

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

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

Issue Reasons:

  • [7.17] 2 consecutive failures in step openjdk23_java-matrix
  • [7.17] 2 failures in test testDefaultSettings (1.6% fail rate in 126 executions)
  • [7.17] 2 failures in step openjdk23_java-matrix (100.0% fail rate in 2 executions)
  • [7.17] 2 failures in pipeline elasticsearch-periodic (50.0% fail rate in 4 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Distributed/Network Http and internode communication implementations >test-failure Triaged test failures from CI labels Oct 4, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine elasticsearchmachine added Team:Distributed Meta label for distributed team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Oct 4, 2024
@DaveCTurner DaveCTurner self-assigned this Oct 4, 2024
@DaveCTurner DaveCTurner mentioned this issue Oct 4, 2024
Closed
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this issue Oct 4, 2024
@DaveCTurner
Flush response stream in Ec2DiscoveryTests
538c517 
This is apparently necessary when running with JDK23. Also cleans up
some warnings in the same test suite.

Closes elastic#114088
Closes elastic#114089
Closes elastic#114090
@DaveCTurner DaveCTurner mentioned this issue Oct 4, 2024
Merged
@DaveCTurner DaveCTurner added low-risk An open issue or test failure that is a low risk to future releases and removed :Distributed/Network Http and internode communication implementations >test-failure Triaged test failures from CI Team:Distributed Meta label for distributed team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Oct 4, 2024
@elasticsearchmachine elasticsearchmachine added the needs:triage Requires assignment of a team area label label Oct 4, 2024
@DaveCTurner DaveCTurner added >test-failure Triaged test failures from CI :Distributed/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure and removed needs:triage Requires assignment of a team area label labels Oct 4, 2024
@elasticsearchmachine elasticsearchmachine added the Team:Distributed Meta label for distributed team label Oct 4, 2024
@DaveCTurner DaveCTurner added low-risk An open issue or test failure that is a low risk to future releases and removed low-risk An open issue or test failure that is a low risk to future releases labels Oct 4, 2024
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this issue Oct 4, 2024
@DaveCTurner
Flush response stream in Ec2DiscoveryTests (elastic#114101)
81c501b 
This is apparently necessary when running with JDK23. Also cleans up
some warnings in the same test suite.

Closes elastic#114088
Closes elastic#114089
Closes elastic#114090
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this issue Oct 4, 2024
@DaveCTurner
Flush response stream in Ec2DiscoveryTests (elastic#114101)
0038f66 
This is apparently necessary when running with JDK23. Also cleans up
some warnings in the same test suite.

Closes elastic#114088
Closes elastic#114089
Closes elastic#114090
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this issue Oct 4, 2024
@DaveCTurner
Flush response stream in Ec2DiscoveryTests (elastic#114101)
fbbdb77 
This is apparently necessary when running with JDK23. Also cleans up
some warnings in the same test suite.

Closes elastic#114088
Closes elastic#114089
Closes elastic#114090
elasticsearchmachine pushed a commit that referenced this issue Oct 4, 2024
@DaveCTurner
[7.17] Flush response stream in Ec2DiscoveryTests (#114101) (#114113)
f751392 
* Flush response stream in `Ec2DiscoveryTests` (#114101)

This is apparently necessary when running with JDK23. Also cleans up
some warnings in the same test suite.

Closes #114088
Closes #114089
Closes #114090

* Revert for compat
elasticsearchmachine pushed a commit that referenced this issue Oct 4, 2024
@DaveCTurner
Flush response stream in Ec2DiscoveryTests (#114101) (#114112)
821212f 
This is apparently necessary when running with JDK23. Also cleans up
some warnings in the same test suite.

Closes #114088
Closes #114089
Closes #114090
elasticsearchmachine pushed a commit that referenced this issue Oct 4, 2024
@DaveCTurner
Flush response stream in Ec2DiscoveryTests (#114101) (#114114)
34251cf 
This is apparently necessary when running with JDK23. Also cleans up
some warnings in the same test suite.

Closes #114088
Closes #114089
Closes #114090
matthewabbott pushed a commit to matthewabbott/elasticsearch that referenced this issue Oct 10, 2024
@DaveCTurner @matthewabbott
Flush response stream in Ec2DiscoveryTests (elastic#114101)
012ecd7 
This is apparently necessary when running with JDK23. Also cleans up
some warnings in the same test suite.

Closes elastic#114088
Closes elastic#114089
Closes elastic#114090
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DaveCTurner DaveCTurner

Labels
:Distributed/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 Meta label for distributed team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Flush response stream in Ec2DiscoveryTests DaveCTurner/elasticsearch
2 participants
@DaveCTurner @elasticsearchmachine