Skip to content

[AUTOCUT] Gradle Check Flaky Test Report for ShardsLimitAllocationDeciderRemoteStoreEnabledIT #17931

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
opensearch-ci-bot opened this issue Apr 14, 2025 · 0 comments
Labels
autocut flaky-test Random test failure that succeeds on second run >test-failure Test failure from CI, local build, etc. untriaged

Comments

@opensearch-ci-bot
Copy link
Collaborator

opensearch-ci-bot commented Apr 14, 2025

Flaky Test Report for ShardsLimitAllocationDeciderRemoteStoreEnabledIT

Noticed the ShardsLimitAllocationDeciderRemoteStoreEnabledIT has some flaky, failing tests that failed during post-merge actions.

Details

Git Reference Merged Pull Request Build Details Test Name
18a3b75 17796 56046 org.opensearch.cluster.routing.allocation.decider.ShardsLimitAllocationDeciderRemoteStoreEnabledIT.testCombinedIndexAndClusterPrimaryShardLimits
3e10fe3 17275 56160 org.opensearch.cluster.routing.allocation.decider.ShardsLimitAllocationDeciderRemoteStoreEnabledIT.testUpdatingIndexPrimaryShardLimit
8ab82a0 17922 56847 org.opensearch.cluster.routing.allocation.decider.ShardsLimitAllocationDeciderRemoteStoreEnabledIT.testIndexPrimaryShardLimit

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autocut flaky-test Random test failure that succeeds on second run >test-failure Test failure from CI, local build, etc. untriaged
Projects
None yet
1 participant