[AUTOCUT] Gradle Check Flaky Test Report for AutoForceMergeManagerTests

[opensearch-ci-bot]

Flaky Test Report for AutoForceMergeManagerTests

Noticed the AutoForceMergeManagerTests has some flaky, failing tests that failed during post-merge actions and timer trigerred run on main branch.

Details

Git Reference	Merged Pull Request	Build Details	Test Name
main	null	60042 60339 61539 62067 62073 62118 62119	org.opensearch.index.autoforcemerge.AutoForceMergeManagerTests.classMethod org.opensearch.index.autoforcemerge.AutoForceMergeManagerTests.testForceMergeOperationOnDataNodeWithThreadInterruption
45e0fab	18990	62043	org.opensearch.index.autoforcemerge.AutoForceMergeManagerTests.classMethod org.opensearch.index.autoforcemerge.AutoForceMergeManagerTests.testForceMergeOperationOnDataNodeWithThreadInterruption
a599cd4	18685	60762	org.opensearch.index.autoforcemerge.AutoForceMergeManagerTests.classMethod org.opensearch.index.autoforcemerge.AutoForceMergeManagerTests.testForceMergeOperationOnDataNodeWithThreadInterruption

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

• 18565
• 18966

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

[andrross]

New test added in #18229

@Harsh-87 Can you take a look?

[andrross]

This looks wrong:

OpenSearch/server/src/test/java/org/opensearch/index/autoforcemerge/AutoForceMergeManagerTests.java

Line 540 in 26ada7e

Thread.sleep(1000L);

The test should be using a concurrency primitive like a latch rather than a fixed sleep.

FYI @gbbafna