Skip to content

[AUTOCUT] Gradle Check Flaky Test Report for FullClusterRestartIT #15813

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 Sep 6, 2024 · 1 comment
Open
Labels
autocut flaky-test Random test failure that succeeds on second run >test-failure Test failure from CI, local build, etc.

Comments

@opensearch-ci-bot
Copy link
Collaborator

opensearch-ci-bot commented Sep 6, 2024

Flaky Test Report for FullClusterRestartIT

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

Details

Git Reference Merged Pull Request Build Details Test Name
97bc5dd 17205 52947 org.opensearch.upgrades.FullClusterRestartIT.testRecoveryWithTranslogRetentionDisabled
d085afe 15309 44793 org.opensearch.upgrades.FullClusterRestartIT.testEmptyShard
d4a76cd 16672 50850 org.opensearch.upgrades.FullClusterRestartIT.testRecoveryWithTranslogRetentionDisabled
9bca961 17617 58523 org.opensearch.upgrades.FullClusterRestartIT.testRecovery
b3ad02a 18421 59113 org.opensearch.upgrades.FullClusterRestartIT.testRecovery
f122c46 17532 56836 org.opensearch.upgrades.FullClusterRestartIT.testRecovery

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

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

@opensearch-ci-bot opensearch-ci-bot added >test-failure Test failure from CI, local build, etc. autocut flaky-test Random test failure that succeeds on second run untriaged labels Sep 6, 2024
@reta
Copy link
Contributor

reta commented Sep 30, 2024

[Catch All Triage - 1, 2, 3, 4]

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.
Projects
None yet
Development

No branches or pull requests

2 participants