Skip to content

[AUTOCUT] Gradle Check Flaky Test Report for CloseIndexIT #18878

@opensearch-ci-bot

Description

@opensearch-ci-bot

Flaky Test Report for CloseIndexIT

Noticed the CloseIndexIT 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
5fd0a36 18808 61327 org.opensearch.indices.state.CloseIndexIT.testCloseAlreadyClosedIndex {p0={"search.concurrent_segment_search.enabled":"false"}}

org.opensearch.indices.state.CloseIndexIT.testCloseIndex {p0={"search.concurrent_segment_search.enabled":"false"}}

org.opensearch.indices.state.CloseIndexIT.testCloseMissingIndex {p0={"search.concurrent_segment_search.enabled":"false"}}

org.opensearch.indices.state.CloseIndexIT.testCloseOneMissingIndexIgnoreMissing {p0={"search.concurrent_segment_search.enabled":"false"}}

org.opensearch.indices.state.CloseIndexIT.testCloseWhileDeletingIndices {p0={"search.concurrent_segment_search.enabled":"false"}}

org.opensearch.indices.state.CloseIndexIT.testConcurrentClose {p0={"search.concurrent_segment_search.enabled":"false"}}

org.opensearch.indices.state.CloseIndexIT.testNoopPeerRecoveriesWhenIndexClosed {p0={"search.concurrent_segment_search.enabled":"false"}}

org.opensearch.indices.state.CloseIndexIT.testRecoverExistingReplica {p0={"search.concurrent_segment_search.enabled":"false"}}

The other pull requests, besides those involved in post-merge actions, that contain failing tests with the CloseIndexIT 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 rununtriaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions