Flaky-test: org.apache.bookkeeper.replication.BookieAutoRecoveryTest.testOpenLedgers
- Dominant language
- Java
- Stars
- 2k
- Forks
- 976
- Avg merge
- 6d 15h
- Merged PRs (30d)
- 7
Description
org.apache.bookkeeper.replication.BookieAutoRecoveryTest.testOpenLedgers is flaky. It fails sporadically.
```
Error: org.apache.bookkeeper.replication.BookieAutoRecoveryTest.testOpenLedgers -- Time elapsed: 120.0 s <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 120 seconds
at java.base@11.0.26/jdk.internal.misc.Unsafe.park(Native Method)
at java.base@11.0.26/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
at java.base@11.0.26/java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:885)
at java.base@11.0.26/java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1039)
at java.base@11.0.26/java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1345)
at java.base@11.0.26/java.util.concurrent.CountDownLatch.await(CountDownLatch.java:232)
at app//org.apache.bookkeeper.replication.BookieAutoRecoveryTest.testOpenLedgers(BookieAutoRecoveryTest.java:[165](https://github.com/apache/bookkeeper/actions/runs/13710867425/job/38414276698?pr=4562#step:7:166))
at java.base@11.0.26/java.lang.reflect.Method.invoke(Method.java:566)
at java.base@11.0.26/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base@11.0.26/java.lang.Thread.run(Thread.java:829)
```
Failed runs:
- https://github.com/apache/bookkeeper/actions/runs/13710867425/job/38349603650
- https://github.com/apache/bookkeeper/actions/runs/13710867425/job/38392082381
- https://github.com/apache/bookkeeper/actions/runs/13710867425/job/38413725380
Contributor guide
Research direction
Start by opening org.apache.bookkeeper.replication.BookieAutoRecoveryTest and running testOpenLedgers repeatedly. Inspect the CountDownLatch.await at line 165 and the linked failed CI runs to determine why the test times out. Done means the test no longer flakes or exceeds its 120-second timeout in repeated 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
- 35/100