Skip to content

[CI] SnapshotShutdownIT testSnapshotShutdownProgressTracker failing #127690

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

Open
elasticsearchmachine opened this issue May 4, 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:

./gradlew ":server:internalClusterTest" --tests "org.elasticsearch.snapshots.SnapshotShutdownIT.testSnapshotShutdownProgressTracker" -Dtests.seed=9FD834DA1359087B -Dtests.locale=xnr-IN -Dtests.timezone=Africa/Mbabane -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: expected to see SnapshotShutdownProgressTracker running number of snapshots but did not
Expected: <true>
     but: was <false>

Issue Reasons:

  • [main] 2 failures in test testSnapshotShutdownProgressTracker (0.3% fail rate in 640 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 May 4, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 failures in test testSnapshotShutdownProgressTracker (0.3% fail rate in 640 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Distributed Coordination Meta label for Distributed Coordination team labels May 4, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@nicktindall nicktindall added medium-risk An open issue or test failure that is a medium risk to future releases 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) medium-risk An open issue or test failure that is a medium risk to future releases labels May 5, 2025
@nicktindall
Copy link
Contributor

nicktindall commented May 5, 2025

The log message doesn't match because numShards is not what is expected. It's not immediately obvious why. This looks like a test for some logging though, so I suspect it's not an indication that snapshots might be broken.

@nicktindall nicktindall added medium-risk An open issue or test failure that is a medium risk to future releases low-risk An open issue or test failure that is a low risk to future releases and removed low-risk An open issue or test failure that is a low risk to future releases medium-risk An open issue or test failure that is a medium risk to future releases labels May 5, 2025
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 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
Development

No branches or pull requests

2 participants