-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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] Flaky test - RemoteReplicaRecoveryIT.testReplicaRecovery() #13473
Labels
bug
Something isn't working
flaky-test
Random test failure that succeeds on second run
Search
Search query, autocomplete ...etc
Storage:Remote
Storage
Issues and PRs relating to data and metadata storage
Comments
8 tasks
8 tasks
peternied
added
Storage:Remote
Storage
Issues and PRs relating to data and metadata storage
and removed
untriaged
labels
May 1, 2024
This was referenced May 3, 2024
8 tasks
9 tasks
9 tasks
7 tasks
7 tasks
7 tasks
6 tasks
This was referenced May 24, 2024
Merged
9 tasks
bowenlan-amzn
added
the
flaky-test
Random test failure that succeeds on second run
label
Jun 3, 2024
This was referenced Jun 4, 2024
3 tasks
3 tasks
9 tasks
Closing in favour of #14303 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
flaky-test
Random test failure that succeeds on second run
Search
Search query, autocomplete ...etc
Storage:Remote
Storage
Issues and PRs relating to data and metadata storage
Describe the bug
RemoteReplicaRecoveryIT.testReplicaRecovery() sometimes fails with 1 less hit than expected. Example here.
Related component
Search
To Reproduce
REPRODUCE WITH: ./gradlew ':server:internalClusterTest' --tests "org.opensearch.remotemigration.RemoteReplicaRecoveryIT.testReplicaRecovery" -Dtests.seed=47558462C4ABB134 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=mk -Dtests.timezone=Etc/GMT-3 -Druntime.java=21
Expected behavior
The test should always pass.
Additional Details
No response
The text was updated successfully, but these errors were encountered: