Skip to content

Conversation

@opensearch-trigger-bot
Copy link
Contributor

Backport ec5adda from #18500.

@opensearch-trigger-bot opensearch-trigger-bot bot requested a review from a team as a code owner June 12, 2025 16:13
@github-actions
Copy link
Contributor

❌ Gradle check result for e4f23be: 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?

Copy link
Contributor

@q-andy q-andy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking care of this

@owaiskazi19
Copy link
Member

@peterzhuamazon any idea why the breaking change workflow is failing for this PR?

@github-actions
Copy link
Contributor

❌ Gradle check result for e4f23be: 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
Copy link
Contributor

❌ Gradle check result for e4f23be: 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?

@q-andy
Copy link
Contributor

q-andy commented Jun 13, 2025

Gradle check failures are all flaky integ tests

org.opensearch.recovery.FullRollingRestartIT.testDerivedSourceWithConcurrentUpdatesRollingRestart
org.opensearch.recovery.RecoveryWhileUnderLoadIT.testRecoverWhileUnderLoadWithDerivedSource
org.opensearch.recovery.RecoveryWhileUnderLoadIT.testReplicaRecoveryWithDerivedSourceFromTranslog
org.opensearch.recovery.RecoveryWhileUnderLoadIT.testRecoverWhileUnderLoadAllocateReplicasTest
org.opensearch.recovery.RecoveryWhileUnderLoadIT.testRecoveryWithDerivedSourceEnabled
org.opensearch.recovery.FullRollingRestartIT.testDerivedSourceWithMixedVersionRollingRestart
org.opensearch.common.ssl.PemTrustConfigTests.testTrustConfigReloadsFileContents

Open issues:
#18490
#14509
#18490
#17745

@github-actions
Copy link
Contributor

❌ Gradle check result for e4f23be: 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?

@q-andy
Copy link
Contributor

q-andy commented Jun 13, 2025

#17693

@peterzhuamazon
Copy link
Member

peterzhuamazon commented Jun 13, 2025

@peterzhuamazon any idea why the breaking change workflow is failing for this PR?

@andrross ^^

@github-actions
Copy link
Contributor

❌ Gradle check result for e4f23be:

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
Copy link
Contributor

❌ Gradle check result for e4f23be: 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
Copy link
Contributor

❌ Gradle check result for e4f23be: 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
Copy link
Contributor

❌ Gradle check result for e4f23be: 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
Copy link
Contributor

❌ Gradle check result for e4f23be: 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
Copy link
Contributor

❌ Gradle check result for e4f23be:

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
Copy link
Contributor

❌ Gradle check result for e4f23be: null

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
Copy link
Contributor

❌ Gradle check result for e4f23be: 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?

…8500)

Signed-off-by: Andy Qin <qinandy@amazon.com>
(cherry picked from commit ec5adda)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@owaiskazi19 owaiskazi19 force-pushed the backport/backport-18500-to-3.1 branch from e4f23be to ac70d2d Compare June 18, 2025 06:32
@github-actions
Copy link
Contributor

✅ Gradle check result for ac70d2d: SUCCESS

@codecov
Copy link

codecov bot commented Jun 18, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (3.1@18ae617). Learn more about missing BASE report.

Additional details and impacted files
@@          Coverage Diff           @@
##             3.1   #18504   +/-   ##
======================================
  Coverage       ?   72.68%           
  Complexity     ?    68124           
======================================
  Files          ?     5537           
  Lines          ?   313379           
  Branches       ?    45474           
======================================
  Hits           ?   227785           
  Misses         ?    67090           
  Partials       ?    18504           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@owaiskazi19 owaiskazi19 merged commit 69bf501 into 3.1 Jun 18, 2025
44 of 47 checks passed
@github-actions github-actions bot deleted the backport/backport-18500-to-3.1 branch June 18, 2025 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants