Skip to content

[CI] GoogleCloudStorageBlobStoreRepositoryTests testRequestStats failing #126902

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

Closed
elasticsearchmachine opened this issue Apr 16, 2025 · 3 comments · Fixed by #126972
Closed
Labels
:Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs needs:risk Requires assignment of a risk label (low, medium, blocker) 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:

./gradlew ":modules:repository-gcs:internalClusterTest" --tests "org.elasticsearch.repositories.gcs.GoogleCloudStorageBlobStoreRepositoryTests.testRequestStats" -Dtests.seed=93BC0B8AE3162E96 -Dtests.locale=fr-BF -Dtests.timezone=Australia/Canberra -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: a value greater than <0>
     but: <0> was equal to <0>

Issue Reasons:

  • [main] 9 failures in test testRequestStats (4.9% fail rate in 182 executions)
  • [main] 7 failures in step part-1 (8.8% fail rate in 80 executions)
  • [main] 6 failures in pipeline elasticsearch-pull-request (7.4% fail rate in 81 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 labels Apr 16, 2025
elasticsearchmachine added a commit that referenced this issue Apr 16, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 9 failures in test testRequestStats (4.9% fail rate in 182 executions)
  • [main] 7 failures in step part-1 (8.8% fail rate in 80 executions)
  • [main] 6 failures in pipeline elasticsearch-pull-request (7.4% fail rate in 81 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added the needs:risk Requires assignment of a risk label (low, medium, blocker) label Apr 16, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine elasticsearchmachine added the Team:Distributed Coordination Meta label for Distributed Coordination team label Apr 16, 2025
@DiannaHohensee
Copy link
Contributor

The failure reproduces reliably on my local machine. I tried reverting 17c6e10 and it started passing again.

@nicktindall (CC: @mhl-b)

I expect #126903, #126908 and #126909 are similar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Distributed Coordination Meta label for Distributed Coordination team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants