[Backport 2.14] [Bugfix] Fix flaky test CacheStatsAPIIndicesRequestCacheIT.testNullLevels() #13485
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.
Original PR: #13457
2.x Backport PR: #13475
Description
I introduced CacheStatsAPIIndicesRequestCacheIT in this recent PR but I have found it to be flaky (example here). I created an issue for this here.
If
levels
is uninitialized in CommonStatsFlags, the String[]levels
passed into DefaultCacheStatsHolder is usually an empty list. This is the expected behavior. But in some cases, DefaultCacheStatsHolder receives null instead of an empty list, and in this case, the XContent output derived from it has unexpected fields. To fix this we add an explicit null check when DefaultCacheStatsHolder constructs the object which produces XContent, and use an empty list if null is passed in.We also initialize CommonStatsFlags.levels to be an empty String[] rather than null, as I found not doing this can rarely cause RestNodesStatsActionTests.testUnrecognizedMetric() to flake for the same reason.
Finally, fixes inconsistency with how null levels were used in tests.
Related Issues
Resolves #13458
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.