opensearch-project / opensearch-project/OpenSearch
[AUTOCUT] Gradle Check Flaky Test Report for IndexRecoveryIT
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 13.7k
- Forks
- 3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 108
Description
Flaky Test Report for IndexRecoveryIT
Noticed the IndexRecoveryIT 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 | 78790 80337 81442 |
org.opensearch.indices.recovery.IndexRecoveryIT.testRecoverLocallyUpToGlobalCheckpointorg.opensearch.indices.recovery.IndexRecoveryIT.testOngoingRecoveryAndClusterManagerFailOver |
| dca99fe9bb80893887378d216e0620edee270b0b | 22092 | 80020 | org.opensearch.indices.recovery.IndexRecoveryIT.testOngoingRecoveryAndClusterManagerFailOver |
| 55e98ed2735d898d884295c00f869f5f3278c222 | 16265 | 49382 | org.opensearch.indices.recovery.IndexRecoveryIT.testRerouteRecovery |
The other pull requests, besides those involved in post-merge actions, that contain failing tests with the IndexRecoveryIT class are:
- 19966
- 13997
- 21247
- 17987
- 14119
- 14618
- 17207
- 17441
- 17741
- 21427
- 21528
- 21767
- 21775
- 21868
- 21871
- 21953
- 22228
For more details on the failed tests refer to OpenSearch Gradle Check Metrics dashboard.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the IndexRecoveryIT tests named in the report, especially testRecoverLocallyUpToGlobalCheckpoint, testOngoingRecoveryAndClusterManagerFailOver, and testRerouteRecovery. Review the linked Gradle Check reports and OpenSearch Gradle Check Metrics dashboard to identify reproducible failure patterns. Done means the flaky failures are understood and the affected tests pass reliably under the relevant runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100