org.junit.runners.model.TestTimedOutException: test timed out after 60000 milliseconds, took 60.003 sec

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by gianm
, 1 year ago
test timed out after 60000 milliseconds, took 60.003 sec
via GitHub by imasahiro
, 4 months ago
test timed out after 20000 milliseconds
via GitHub by gfrison
, 1 year ago
test timed out after 60000 milliseconds
via GitHub by dpwspoon
, 7 months ago
test timed out after 7 seconds
via GitHub by Donnerbart
, 1 year ago
test timed out after 60000 milliseconds
org.junit.runners.model.TestTimedOutException: test timed out after 60000 milliseconds, took 60.003 sec
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
at com.metamx.tranquility.kafka.KafkaConsumerTest.testStartConsumersNoCommit(KafkaConsumerTest.java:220)

Users with the same issue

Once, 5 months ago
Once, 2 months ago

Know the solutions? Share your knowledge to help other developers to debug faster.