Skip to content

[AUTOCUT] Gradle Check Flaky Test Report for SegmentReplicationSuiteIT #19258

@opensearch-ci-bot

Description

@opensearch-ci-bot

Flaky Test Report for SegmentReplicationSuiteIT

Noticed the SegmentReplicationSuiteIT 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 70910

63333

68670

68713

68721

68797

68847

68867

68980

69075

69077

69163

69168

69247

69325

69362

69503

69560

69720

69808

69858

69883

69884

69970

70295

70438

70475

70584

70713

70823

71162
org.opensearch.indices.replication.SegmentReplicationSuiteIT.testFullRestartDuringReplication

org.opensearch.indices.replication.SegmentReplicationSuiteIT.testDropRandomNodeDuringReplication

org.opensearch.indices.replication.SegmentReplicationSuiteIT.testDeleteIndexWhileReplicating
985b0c8 20565 71065 org.opensearch.indices.replication.SegmentReplicationSuiteIT.testFullRestartDuringReplication
0d58b07 20471 70675 org.opensearch.indices.replication.SegmentReplicationSuiteIT.testFullRestartDuringReplication
eeec4d9 20482 70517 org.opensearch.indices.replication.SegmentReplicationSuiteIT.testDropRandomNodeDuringReplication
8a0f3a6 20303 69161 org.opensearch.indices.replication.SegmentReplicationSuiteIT.testFullRestartDuringReplication

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

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    >test-failureTest failure from CI, local build, etc.autocutflaky-testRandom test failure that succeeds on second run

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions