-
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
flaky test fix - assert cluster stats on ClusterManager Node #13383
flaky test fix - assert cluster stats on ClusterManager Node #13383
Conversation
❌ Gradle check result for dbfb860: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
…cal to the node Signed-off-by: Rajiv Kumar Vaidyanathan <rajivkv@amazon.com>
dbfb860
to
9300535
Compare
❌ Gradle check result for 9300535: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
org.opensearch.cluster.allocation.ClusterRerouteIT.testDelayWithALargeAmountOfShards |
❌ Gradle check result for 9300535: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #13383 +/- ##
===========================================
Coverage 71.42% 71.42%
- Complexity 59978 60654 +676
===========================================
Files 4985 5039 +54
Lines 282275 285445 +3170
Branches 40946 41341 +395
===========================================
+ Hits 201603 203871 +2268
- Misses 63999 64757 +758
- Partials 16673 16817 +144 ☔ View full report in Codecov by Sentry. |
Fixes #11063 |
Description
The fix is for flaky test ClusterManagerDisruptionIT#testIsolateClusterManagerAndVerifyClusterStateConsensus where the verification of ClusterStateStats was failing. The test was asserting on the ClusterStats which was retrieved from a random node in cluster. However ClusterStateStats is local to a node and has to be verified on node which was ClusterManager before the disruption was started.
Related Issues
Resolves #[11063]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.