[AUTOCUT] Gradle Check Flaky Test Report for RecoveryIT #15811
Labels
autocut
flaky-test
Random test failure that succeeds on second run
>test-failure
Test failure from CI, local build, etc.
Uh oh!
There was an error while loading. Please reload this page.
Flaky Test Report for
RecoveryIT
Noticed the
RecoveryIT
has some flaky, failing tests that failed during post-merge actions.Details
org.opensearch.upgrades.RecoveryIT.testAutoExpandIndicesDuringRollingUpgrade
org.opensearch.upgrades.RecoveryIT.testClosedIndexNoopRecovery
org.opensearch.upgrades.RecoveryIT.testRelocationWithConcurrentIndexing
org.opensearch.upgrades.RecoveryIT.testAutoExpandIndicesDuringRollingUpgrade
org.opensearch.upgrades.RecoveryIT.testCloseIndexDuringRollingUpgrade
org.opensearch.upgrades.RecoveryIT.testRelocationWithConcurrentIndexing
org.opensearch.upgrades.RecoveryIT.testRecoveryWithConcurrentIndexing
org.opensearch.upgrades.RecoveryIT.testRelocationWithConcurrentIndexing
org.opensearch.upgrades.RecoveryIT.testRelocationWithConcurrentIndexing
org.opensearch.upgrades.RecoveryIT.testRetentionLeasesEstablishedWhenRelocatingPrimary
org.opensearch.upgrades.RecoveryIT.testRelocationWithConcurrentIndexing
org.opensearch.upgrades.RecoveryIT.testRetentionLeasesEstablishedWhenRelocatingPrimary
org.opensearch.upgrades.RecoveryIT.testRelocationWithConcurrentIndexing
org.opensearch.upgrades.RecoveryIT.testRetentionLeasesEstablishedWhenRelocatingPrimary
The other pull requests, besides those involved in post-merge actions, that contain failing tests with the
RecoveryIT
class are:For more details on the failed tests refer to OpenSearch Gradle Check Metrics dashboard.
The text was updated successfully, but these errors were encountered: