[AUTOCUT] Gradle Check Flaky Test Report for TieredSpilloverCacheStatsIT

[opensearch-ci-bot]

Flaky Test Report for TieredSpilloverCacheStatsIT

Noticed the TieredSpilloverCacheStatsIT has some flaky, failing tests that failed during post-merge actions.

Details

Git Reference	Merged Pull Request	Build Details	Test Name
0dcb617	14160	40642	org.opensearch.cache.common.tier.TieredSpilloverCacheStatsIT.testStatsMatchOldApi
0fff808	14241	40860	org.opensearch.cache.common.tier.TieredSpilloverCacheStatsIT.testStatsMatchOldApi
1b36ee4	13926	40314	org.opensearch.cache.common.tier.TieredSpilloverCacheStatsIT.testStatsMatchOldApi
2f8cb07	13821	40754	org.opensearch.cache.common.tier.TieredSpilloverCacheStatsIT.testStatsMatchOldApi
3bb0b4a	14059	40115	org.opensearch.cache.common.tier.TieredSpilloverCacheStatsIT.testIndicesLevelAggregation
698f582	14344	41003	org.opensearch.cache.common.tier.TieredSpilloverCacheStatsIT.testStatsMatchOldApi
8af4647	14182	40937	org.opensearch.cache.common.tier.TieredSpilloverCacheStatsIT.testIndicesAndTierLevelAggregation
d2da9bb	14061	40216	org.opensearch.cache.common.tier.TieredSpilloverCacheStatsIT.testStatsMatchOldApi
d480027	14341	41019	org.opensearch.cache.common.tier.TieredSpilloverCacheStatsIT.testIndicesLevelAggregation

The other pull requests, besides those involved in post-merge actions, that contain failing tests with the TieredSpilloverCacheStatsIT class are:

• 12982
• 13998
• 14104
• 13172
• 13474
• 13568
• 13739
• 13772
• 13834
• 13917
• 14062
• 14089
• 14119
• 14136
• 14154
• 14155
• 14206
• 14216
• 14230
• 14264
• 14338
• 14339
• 14357
• 14360
• 14362
• 14391
• 14487

For more details on the failed tests refer to OpenSearch Gradle Check Metrics dashboard.

[getsaurabh02]

@sgup432 Can you take a stab at this?

[sgup432]

@peteralfonsi Can you check on this? Considering you resolved all of them earlier.

[peteralfonsi]

This issue has been solved by #14333. We are still seeing a couple failures, but I've been going through and all those failures are on PRs from branches that don't yet have the fix in them.

I think we can leave this issue open for a couple more days so that people who have outstanding PRs without the fix in them can refer to it, and then close it assuming no actual new failures happen.