AnonHxy opened a new issue, #4109:
URL: https://github.com/apache/bookkeeper/issues/4109

   <!--- 
   
   Instructions for reporting a flaky test using this issue template:
   
   1. Replace test_class in title and body with the short test class name 
WITHOUT the package name.
   2. Replace test_method in title and body with the test method that failed. 
Multiple methods are flaky, remove the content that refers to the test method.
   3. Replace "relevant parts of the exception stacktrace here" with the a few 
lines of the stack trace that shows at least the exception message and the line 
of test code where the stacktrace occurred.
   4. Replace "full exception stacktrace here" with the full exception 
stacktrace from logs. This section will be hidden by default.
   5. Remove all unused fields / content to unclutter the reported issue. 
Remove this comment too.
   
   -->
   `HandleFailuresTest.testHandleFailureBookieNotInWriteSet` is flaky. It fails 
sporadically.
   
   ```
   Error:  
org.apache.bookkeeper.client.HandleFailuresTest.testHandleFailureBookieNotInWriteSet
  Time elapsed: 30.008 s  <<< ERROR!
   org.junit.runners.model.TestTimedOutException: test timed out after 30000 
milliseconds
        at [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
        at 
[email protected]/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
        at 
[email protected]/java.util.concurrent.CompletableFuture$Signaller.block(CompletableFuture.java:1796)
        at 
[email protected]/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3128)
        at 
[email protected]/java.util.concurrent.CompletableFuture.waitingGet(CompletableFuture.java:1823)
        at 
[email protected]/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1998)
        at 
app//org.apache.bookkeeper.client.HandleFailuresTest.testHandleFailureBookieNotInWriteSet(HandleFailuresTest.java:484)
        at 
[email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
 Method)
        at 
[email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at 
[email protected]/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at [email protected]/java.lang.reflect.Method.invoke(Method.java:566)
        at 
app//org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
        at 
app//org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
        at 
app//org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
        at 
app//org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
        at 
app//org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
        at 
app//org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:[292](https://github.com/apache/bookkeeper/actions/runs/6438330917/job/17597911178?pr=4098#step:8:293))
        at 
[email protected]/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at [email protected]/java.lang.Thread.run(Thread.java:829)
   ```
   
   <!-- optionally provide the full stacktrace ->
   <details>
   <summary>Full exception stacktrace</summary>
   <code><pre>
   full exception stacktrace here
   </pre></code>
   </details>
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to