-
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] org.opensearch.cluster.MinimumClusterManagerNodesIT.testThreeNodesNoClusterManagerBlock flaky #10006
Labels
bug
Something isn't working
Cluster Manager
flaky-test
Random test failure that succeeds on second run
Comments
sohami
added
bug
Something isn't working
flaky-test
Random test failure that succeeds on second run
labels
Sep 12, 2023
6 tasks
6 tasks
This was referenced Sep 22, 2023
This was referenced Sep 22, 2023
7 tasks
6 tasks
7 tasks
Merged
7 tasks
This was referenced Oct 21, 2023
8 tasks
8 tasks
Merged
8 tasks
7 tasks
8 tasks
8 tasks
8 tasks
This was referenced May 14, 2024
Merged
|
9 tasks
8 tasks
9 tasks
This was referenced Jun 3, 2024
9 tasks
8 tasks
6 tasks
3 tasks
9 tasks
3 tasks
Closing in favor of the autocut #14289 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
Cluster Manager
flaky-test
Random test failure that succeeds on second run
Describe the bug
Test
org.opensearch.cluster.MinimumClusterManagerNodesIT.testThreeNodesNoClusterManagerBlock
is flakyTo Reproduce
Expected behavior
Test should always pass
Plugins
Standard
Screenshots
Host/Environment (please complete the following information):
https://build.ci.opensearch.org/job/gradle-check/25287/testReport/junit/org.opensearch.cluster/MinimumClusterManagerNodesIT/testThreeNodesNoClusterManagerBlock/
Additional context
https://build.ci.opensearch.org/job/gradle-check/25287/
I (@andrross) am adding the content from this comment to the description here because it has now been buried in the comment stream:
I believe I have traced this back to the commit that introduced the flakiness: 9119b6d (#9105)
The following command will reliably reproduce the failure for me:
If I select the commit immediately preceding 9119b6d then it does not reproduce.
This is a bit concerning because the commit in question is related to the remote store feature but MinimumClusterManagerNodesIT does not do anything related to remote store, so it is possible there is a significant regression here.
The text was updated successfully, but these errors were encountered: