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] RepositoryGcsClientYamlTestSuiteIT class failing #124615

Open
elasticsearchmachine opened this issue Mar 12, 2025 · 3 comments
Open

[CI] RepositoryGcsClientYamlTestSuiteIT class failing #124615

elasticsearchmachine opened this issue Mar 12, 2025 · 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

Build Scans:

Reproduction Line:

undefined

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

undefined

Issue Reasons:

  • [main] 2 failures in class org.elasticsearch.repositories.gcs.RepositoryGcsClientYamlTestSuiteIT (0.2% fail rate in 813 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 Mar 12, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@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 12, 2025
@nicktindall
Copy link
Contributor

nicktindall commented Mar 12, 2025 •
edited
Loading

Marking this as low risk because I suspect it might be environmental. In fact the two failures linked are different failures and both seem to be for different environmental reasons. I'm tempted to close this.

@mhl-b
Copy link
Contributor

mhl-b commented Mar 12, 2025

Scan failed on my PR, during iterations, which is expected #122991

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
3 participants
@nicktindall @mhl-b @elasticsearchmachine