Skip to content

[CI] GoogleCloudStorageBlobStoreRepositoryTests testWriteReadLarge failing #126903

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
Closed
elasticsearchmachine opened this issue Apr 16, 2025 · 2 comments · Fixed by #126972
Closed

[CI] GoogleCloudStorageBlobStoreRepositoryTests testWriteReadLarge failing #126903

elasticsearchmachine opened this issue Apr 16, 2025 · 2 comments · Fixed by #126972
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

elasticsearchmachine commented Apr 16, 2025 •
edited
Loading

Build Scans:

Reproduction Line:

./gradlew ":modules:repository-gcs:internalClusterTest" --tests "org.elasticsearch.repositories.gcs.GoogleCloudStorageBlobStoreRepositoryTests.testSnapshotWithLargeSegmentFiles" -Dtests.seed=E66EB002C30886C5 -Dtests.locale=ccp-Cakm-BD -Dtests.timezone=America/Regina -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] 4 consecutive failures in test testWriteReadLarge
  • [main] 3 consecutive failures in step part1
  • [main] 3 consecutive failures in step part-1
  • [main] 3 consecutive failures in pipeline elasticsearch-intake
  • [main] 3 consecutive failures in pipeline elasticsearch-pull-request
  • [main] 9 failures in test testWriteReadLarge (4.9% fail rate in 184 executions)
  • [main] 3 failures in step part1 (12.0% fail rate in 25 executions)
  • [main] 6 failures in step part-1 (7.4% fail rate in 81 executions)
  • [main] 3 failures in pipeline elasticsearch-intake (12.0% fail rate in 25 executions)
  • [main] 5 failures in pipeline elasticsearch-pull-request (6.2% 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
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 consecutive failures in test testWriteReadLarge
  • [main] 2 consecutive failures in step part1
  • [main] 2 consecutive failures in pipeline elasticsearch-intake
  • [main] 5 failures in test testWriteReadLarge (2.7% fail rate in 182 executions)
  • [main] 2 failures in step part1 (8.3% fail rate in 24 executions)
  • [main] 3 failures in step part-1 (3.8% fail rate in 80 executions)
  • [main] 2 failures in pipeline elasticsearch-intake (8.3% fail rate in 24 executions)
  • [main] 3 failures in pipeline elasticsearch-pull-request (3.7% fail rate in 81 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Apr 16, 2025
@elasticsearchmachine
Mute org.elasticsearch.repositories.gcs.GoogleCloudStorageBlobStoreRe…
e28fca2 
…positoryTests testWriteReadLarge #126903
@elasticsearchmachine elasticsearchmachine added needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Distributed Coordination Meta label for Distributed Coordination team labels Apr 16, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@DiannaHohensee DiannaHohensee mentioned this issue Apr 16, 2025
Closed
@nicktindall nicktindall mentioned this issue Apr 17, 2025
Merged
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 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
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix GCS tests broken by idempotency token nicktindall/elasticsearch
1 participant
@elasticsearchmachine