Fix flaky test assertion in testScaleUpCluster by using Set compariso… #12211
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Description
The fix addressed flaky test failures in the
KafkaMirrorMaker2AssemblyOperatorPodSetTest.javafile, specifically in thetestScaleUpClustermethod, where assertions on the labelSelector field were failing intermittently due to non-deterministic HashMap iteration order, as HashMap order is not always promised. Using NonDex, a tool that shuffles method executions to expose order-dependent bugs, I ran the tests over 100 times to confirm the flakiness stemmed from varying comma-separated label strings(e.g., "strimzi.io/cluster=my-mm2,strimzi.io/name=my-mm2-mirrormaker2,strimzi.io/kind=KafkaMirrorMaker2" vs. reordered versions). To resolve this, I replaced the direct string equality assertion with a Set-based comparison, splitting the labelSelector by commas and comparing unordered Sets, ensuring order independence and eliminating the HashMap variability.Checklist
Please go through this checklist and make sure all applicable tasks have been done