[AUTOCUT] Gradle Check Flaky Test Report for RemoteStoreClusterStateRestoreIT

[opensearch-ci-bot]

Flaky Test Report for RemoteStoreClusterStateRestoreIT

Noticed the RemoteStoreClusterStateRestoreIT 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
cdbb76e	18826	61013	org.opensearch.remotestore.RemoteStoreClusterStateRestoreIT.testFullClusterRestoreMultipleIndices
ccf5289	14221	40884	org.opensearch.remotestore.RemoteStoreClusterStateRestoreIT.testFullClusterRestoreGlobalMetadata

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

• 13924
• 16384
• 15557
• 16831
• 13637
• 15330
• 17304
• 14631
• 18944
• 13865
• 14811
• 15107
• 16409
• 14264
• 14338
• 14345
• 15426
• 15476
• 15950

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

[shiv0408]

This test should not be flaky now, the fix was merged in #14230

[shiv0408]

@prudhvigodithi Wanted to confirm if a test becomes flaky again after the issue has been resolved, does our workflow create a new issue or open the previous closed issue?

[prudhvigodithi]

Hey @shiv0408 yes the automation will re-open the issue if it was closed within 3 days (which is configurable) else it will re-create a new issue. In both cases the issue body will have the latest flaky test information.
Thanks
@getsaurabh02

[shiv0408]

@andrross Do you know how this issue got re-opened? I closed the issue as the fix was made, do we need to keep the issue open?

[andrross]

@shiv0408 This is the PR that caused it to reopen: #14345

I think @prudhvigodithi is looking into a similar case. It might be that a PR is open that hasn't rebased with your fix, and that causes it to reopen if the test fails.

[shiv0408]

This PR was merged 3 days ago, but the CI bot opened is couple of hours ago.