add TestIssueLogging on flaky test - org.opensearch.remotestore.RemoteStoreRestoreIT.testRTSRestoreWithNoDataPostRefreshPrimaryReplicaDown

[linuxpi]

Description

• Adds test logging to debug flaky test.
• Flaky Test org.opensearch.remotestore.RemoteStoreRestoreIT.testRTSRestoreWithNoDataPostRefreshPrimaryReplicaDown is not repro-able in local environment even after 5k iteration.
• To be able to understand the root cause of flakyness, we need to get trace logging when this test fails.
• Changes in the PR will ensure whenever this test fails in any PR gradle check, we get trace logging to be able to find the root cause and fix

Related Issues

Relates to #11085

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)
• Public documentation issue/PR created

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.

[github-actions]

❌ Gradle check result for 6ba7690: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[dblock]

@linuxpi this links to an ES bug? Can you explain what you're trying to do please?

[linuxpi]

@linuxpi this links to an ES bug? Can you explain what you're trying to do please?

@dblock this is related to a flaky bug - #11085 . We are enabling trace logging for test failures in PR builds to get to the root cause of the flakyness

[github-actions]

❌ Gradle check result for 2b98296: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for e357656: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for bb3c707: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for cbae09f: SUCCESS

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.62%. Comparing base (b15cb0c) to head (e1466b5).
Report is 264 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #13489      +/-   ##
============================================
+ Coverage     71.42%   71.62%   +0.20%     
- Complexity    59978    61105    +1127     
============================================
  Files          4985     5051      +66     
  Lines        282275   287119    +4844     
  Branches      40946    41602     +656     
============================================
+ Hits         201603   205658    +4055     
- Misses        63999    64467     +468     
- Partials      16673    16994     +321     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dblock]

The link is to elastic/elasticsearch, it should be opensearch-project/OpenSearch

[linuxpi]

The link is to elastic/elasticsearch, it should be opensearch-project/OpenSearch

thanks @dblock for catching this. i thought you were referring to the link in description. I've corrected the link now

[github-actions]

❌ Gradle check result for e89dbdc: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[dblock]

@linuxpi Noticed your empty commit to retrigger gradle check. You can do a git commit --amend and force push with -f to avoid that.

[github-actions]

❌ Gradle check result for f35bc18: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[linuxpi]

@linuxpi Noticed your empty commit to retrigger gradle check. You can do a git commit --amend and force push with -f to avoid that.

Thanks for the suggestion @dblock . Was trying to avoid force pushes but i guess just amending last commit might not be an issue

[github-actions]

✅ Gradle check result for c4ff6de: SUCCESS

[github-actions]

✅ Gradle check result for e1466b5: SUCCESS

[linuxpi]

@dblock can you check if the PR looks good now?