opensearch-project / opensearch-project/OpenSearch
[AUTOCUT] Gradle Check Flaky Test Report for CompositeIndexWriterForAppendTests
Open
@RS146BIJAY is already working on this.
Since Nov 20, 2025.
>test-failure
autocut
disabled-test
flaky-test
- Dominant language
- Java
- Stars
- 13.7k
- Forks
- 3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 108
Description
Flaky Test Report for CompositeIndexWriterForAppendTests
Noticed the CompositeIndexWriterForAppendTests 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 | 70310 71164 72417 68066 68477 69236 70494 70720 71058 71406 72648 72657 |
org.opensearch.index.engine.CompositeIndexWriterForAppendTests.classMethodorg.opensearch.index.engine.CompositeIndexWriterForAppendTests.testConcurrentIndexAndDeleteDuringRefreshorg.opensearch.index.engine.CompositeIndexWriterForAppendTests.testConcurrentIndexingDuringRefresh |
| 14749f77ed5f69dde5dd612c832c02e1be7fd94f | 20607 | 71450 | org.opensearch.index.engine.CompositeIndexWriterForAppendTests.classMethodorg.opensearch.index.engine.CompositeIndexWriterForAppendTests.testConcurrentIndexingDuringRefresh |
| 6966267722419e7a478305313c0ddaafd37213ee | 19765 | 67313 | org.opensearch.index.engine.CompositeIndexWriterForAppendTests.testConcurrentIndexAndDeleteDuringRefresh |
The other pull requests, besides those involved in post-merge actions, that contain failing tests with the CompositeIndexWriterForAppendTests class are:
- 19098
- 20250
- 20447
- 20511
- 20514
- 20584
- 20701
- 20920
- 18890
- 19115
- 19241
- 19352
- 19933
- 20065
- 20257
- 20284
- 20427
- 20526
- 20695
- 20788
- 20792
- 20802
- 20810
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.
Assessment
This issue has not been assessed yet.