[AUTOCUT] Gradle Check Flaky Test Report for TopHitsIT

[opensearch-ci-bot]

Flaky Test Report for TopHitsIT

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

Details

Git Reference	Merged Pull Request	Build Details	Test Name
3d1fa98	13172	40197	org.opensearch.search.aggregations.metrics.TopHitsIT.testFieldCollapsing {p0={"search.concurrent_segment_search.enabled":"true"}}

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

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

[jed326]

Taking a look at this one

[jed326]

java.lang.AssertionError: Unexpected ShardFailures: [shard [[ZGVH1eqWR-m0HunwuGpJBg][field-collapsing][1]], reason [RemoteTransportException[[java.util.ConcurrentModificationException]]; nested: ResponseHandlerFailureTransportException[java.util.ConcurrentModificationException]; nested: ConcurrentModificationException; ], cause [ResponseHandlerFailureTransportException[java.util.ConcurrentModificationException]; nested: ConcurrentModificationException;
Caused by: java.util.ConcurrentModificationException
	at java.base/java.util.HashMap$HashIterator.nextNode(HashMap.java:1605)
	at java.base/java.util.HashMap$EntryIterator.next(HashMap.java:1638)
	at java.base/java.util.HashMap$EntryIterator.next(HashMap.java:1636)
	at java.base/java.util.HashMap.putMapEntries(HashMap.java:519)
	at java.base/java.util.HashMap.<init>(HashMap.java:492)
	at org.opensearch.common.util.concurrent.ThreadContext$ThreadContextStruct.putResponseHeaders(ThreadContext.java:709)
	at org.opensearch.common.util.concurrent.ThreadContext.lambda$newStoredContext$4(ThreadContext.java:278)
	at org.opensearch.common.util.concurrent.ThreadContext$StoredContext.restore(ThreadContext.java:568)
	at org.opensearch.common.util.concurrent.ThreadContext.lambda$wrapRestorable$5(ThreadContext.java:317)
	at org.opensearch.transport.TransportService$ContextRestoreResponseHandler.handleResponse(TransportService.java:1482)

This was fixed in #14084 by @ansjcy

[jed326]

Hmm @andrross did I miss a step when trying to close this out? Not sure why it got re-opened by the automation

[andrross]

@jed326 There's some work in flight to improve the automation, but for now it is expected for issues to be reopened like this

[dblock]

[Catch All Triage - Attendees 1, 2, 3, 4, 5]

[sandeshkr419]

@prudhvigodithi Should we close out this issue since it was not reported to be flaky after Jun 13 - will ci-bot recreate it if the issue persists?

[sandeshkr419]

Tests not reported flaky in around 6 months. Closing this out. ci-bot should reopen in case of any new failures.