-
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] org.opensearch.gateway.remote.RemoteClusterStateCleanupManagerIT.testRemoteCleanupDeleteStale is flaky #13968
Labels
bug
Something isn't working
ClusterManager:RemoteState
flaky-test
Random test failure that succeeds on second run
untriaged
Comments
reta
added
bug
Something isn't working
untriaged
flaky-test
Random test failure that succeeds on second run
labels
Jun 4, 2024
9 tasks
9 tasks
After running multiple times, was able to reproduce this is in local. Seems like delete task was still scheduled when we closed the test. Seems like we might be sharing the same single threaded pool for delete task and assert statement. As when the assert call is causing the thread to sleep, deletion task is still waiting to be executed when the test is closed.
|
This was referenced Jun 4, 2024
Closing, since #13969 was reverted |
|
github-project-automation
bot
moved this from ✅ Done
to 🏗 In progress
in Storage Project Board
Jun 12, 2024
9 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
ClusterManager:RemoteState
flaky-test
Random test failure that succeeds on second run
untriaged
Describe the bug
The test case
org.opensearch.gateway.remote.RemoteClusterStateCleanupManagerIT.testRemoteCleanupDeleteStale
is flaky:Related component
Storage:Remote
To Reproduce
Expected behavior
The test must always pass
Additional Details
Plugins
Standard
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: