paul-rogers opened a new issue, #12869:
URL: https://github.com/apache/druid/issues/12869

   The UT `CuratorDruidCoordinatorTest.testMoveSegment` failed in [this 
build](https://app.travis-ci.com/github/apache/druid/jobs/578851686) with a 
timeout:
   
   ```text
   [ERROR] Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 
60.211 s <<< FAILURE! - in 
org.apache.druid.server.coordinator.CuratorDruidCoordinatorTest
   [ERROR] 
org.apache.druid.server.coordinator.CuratorDruidCoordinatorTest.testMoveSegment 
 Time elapsed: 60.017 s  <<< ERROR!
   org.junit.runners.model.TestTimedOutException: test timed out after 60 
seconds
        at sun.misc.Unsafe.park(Native Method)
        at 
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
        at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
        at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
        at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
        at org.apache.curator.test.Timing.awaitLatch(Timing.java:120)
        at 
org.apache.druid.server.coordinator.CuratorDruidCoordinatorTest.testMoveSegment(CuratorDruidCoordinatorTest.java:411)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
        at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
        at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
        at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
        at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
        at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
        at 
org.apache.druid.testing.DeadlockDetectingFailOnTimeout$CallableStatement.call(DeadlockDetectingFailOnTimeout.java:287)
        at 
org.apache.druid.testing.DeadlockDetectingFailOnTimeout$CallableStatement.call(DeadlockDetectingFailOnTimeout.java:278)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.lang.Thread.run(Thread.java:748)
   [ERROR] 
org.apache.druid.server.coordinator.CuratorDruidCoordinatorTest.testMoveSegment 
 Time elapsed: 60.017 s  <<< ERROR!
   java.lang.Exception: Appears to be stuck in thread Time-limited 
test-SendThread(127.0.0.1:41537)
        at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
        at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
        at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
        at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
        at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
        at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:347)
        at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1223)
   ```
   
   The PR in question refactors SQL code, but changed nothing in the 
coordinator. This same test passed on this branch in previous runs. Conclusion: 
test is flaky.
   
   Theory: Travis has been overloaded of late. Perhaps Travis execution is slow 
and our test timeouts, optimized for a single-user Mac, are too aggressive for 
an overloaded shared system.


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to