Fix flaky test testAssembleQueryConfigUrl. #4083
Merged
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.
Fix flaky test testAssembleQueryConfigUrl due to the non-deterministic iteration order of HashMap.
This flaky test is found by using Nondex, a tool used to find flaky tests in Java projects. The assertion on Line#361 in
RemoteConfigRepositoryTest.java
may fail because the order of two entries,someKey
andanotherKey
, is non-deterministic, so the converted string ofqueryConfigUrl
is non-deterministic, resulting in the flaky test. To fix this test, the data structure of thedetails
field ofApolloNotificationMessages
is changed fromHashMap
toTreeMap
so that the entries of the map is sorted. As a result, the iteration order is deterministic and the test will always pass.