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] S3ServiceTests testRetryOn403RetryPolicy failing #115986

Open
elasticsearchmachine opened this issue Oct 30, 2024 · 2 comments · May be fixed by #115993
Open

[CI] S3ServiceTests testRetryOn403RetryPolicy failing #115986

elasticsearchmachine opened this issue Oct 30, 2024 · 2 comments · May be fixed by #115993
Assignees
Labels
:Distributed/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 Meta label for distributed team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ":modules:repository-s3:test" --tests "org.elasticsearch.repositories.s3.S3ServiceTests.testRetryOn403RetryPolicy" -Dtests.seed=BF0C337BCF56BD88 -Dtests.locale=en-PN -Dtests.timezone=America/Argentina/Salta -Druntime.java=22

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: null

Issue Reasons:

  • [main] 4 failures in test testRetryOn403RetryPolicy (0.8% fail rate in 490 executions)
  • [main] 2 failures in step part-1 (0.9% fail rate in 234 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (0.9% fail rate in 232 executions)

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

@elasticsearchmachine elasticsearchmachine added :Distributed/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >test-failure Triaged test failures from CI labels Oct 30, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 4 failures in test testRetryOn403RetryPolicy (0.8% fail rate in 490 executions)
  • [main] 2 failures in step part-1 (0.9% fail rate in 234 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (0.9% fail rate in 232 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:Distributed Meta label for distributed team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Oct 30, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@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 Oct 31, 2024
@ywangd ywangd self-assigned this Oct 31, 2024
ywangd added a commit to ywangd/elasticsearch that referenced this issue Oct 31, 2024
AWS's default retry condition defines a list of retryable error status.
They are retryable for the custom retryable_403 condition as well. This
PR enhances the test to excercise this logic correctly.

Resolves: elastic#115986
@ywangd ywangd linked a pull request Oct 31, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/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 Meta label for distributed team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants