-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[BUG] Test org.opensearch.snapshots.RestoreSnapshotIT.testRestoreInSameRemoteStoreEnabledIndex is Flaky #8352
Comments
Found another on #8382 and it was reproducible locally.
|
@harishbhakuni21 Can you please take a look? |
Had a quick look into this flaky test. It fails with multiple type of failures. Here are few failures:
|
By making following changes, few of the above failures are fixed: -> Change L351 to But after running for few iterations with above fix I still see
Needs more deep dive |
Fixed in #8422 |
Describe the bug
A clear and concise description of what the bug is.
org.opensearch.snapshots.RestoreSnapshotIT.testRestoreInSameRemoteStoreEnabledIndex is flaky.
Full stack trace: here
To Reproduce
Steps to reproduce the behavior:
./gradlew ':server:internalClusterTest' --tests "org.opensearch.snapshots.RestoreSnapshotIT.testRestoreInSameRemoteStoreEnabledIndex" -Dtests.seed=D34AC87DB7FB7699 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=de-AT -Dtests.timezone=America/Nuuk -Druntime.java=17
Expected behavior
A clear and concise description of what you expected to happen.
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: