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] S3BlobContainerRetriesTests testReadRetriesAfterMeaningfulProgress failing #116543

Closed
elasticsearchmachine opened this issue Nov 9, 2024 · 3 comments
Closed

[CI] S3BlobContainerRetriesTests testReadRetriesAfterMeaningfulProgress failing #116543

elasticsearchmachine opened this issue Nov 9, 2024 · 3 comments
Labels
:Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs 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 Nov 9, 2024 •
edited
Loading

Build Scans:

Reproduction Line:

./gradlew ':modules:repository-s3:test' --tests "org.elasticsearch.repositories.s3.S3BlobContainerRetriesTests.testReadRetriesAfterMeaningfulProgress" -Dtests.seed=B3905FCE37BA801F -Dtests.locale=ar-EH -Dtests.timezone=America/Los_Angeles -Druntime.java=23

Applicable branches:
8.15

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

com.amazonaws.SdkClientException: Unable to execute HTTP request: The target server failed to respond

Issue Reasons:

  • [8.15] 2 consecutive failures in step openjdk23_checkpart1_java-matrix
  • [8.15] 10 failures in test testReadRetriesAfterMeaningfulProgress (1.6% fail rate in 627 executions)
  • [8.15] 10 failures in step openjdk23_checkpart1_java-matrix (45.5% fail rate in 22 executions)
  • [8.15] 10 failures in pipeline elasticsearch-periodic (45.5% fail rate in 22 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >test-failure Triaged test failures from CI needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Distributed Coordination Meta label for Distributed Coordination team labels Nov 9, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@ywangd
Copy link
Member

ywangd commented Nov 10, 2024

Similar to #115583. Will backport the fix #115177

@ywangd
Copy link
Member

ywangd commented Nov 10, 2024

#116556

@ywangd ywangd 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 Nov 10, 2024
@ywangd ywangd mentioned this issue Nov 10, 2024
Merged
@ywangd ywangd closed this as completed Nov 11, 2024
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/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs 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

No branches or pull requests
2 participants
@ywangd @elasticsearchmachine