org.junit.runners.model.TestTimedOutException: test timed out after 60000 milliseconds

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 hasancelik
, 1 year ago
test timed out after 60000 milliseconds
via GitHub by vbekiaris
, 1 year ago
test timed out after 60000 milliseconds
via GitHub by hasancelik
, 1 year ago
test timed out after 60000 milliseconds
via GitHub by Donnerbart
, 1 year ago
test timed out after 60000 milliseconds
via GitHub by hasancelik
, 1 year ago
test timed out after 120000 milliseconds
via GitHub by gianm
, 1 year ago
test timed out after 60000 milliseconds, took 60.003 sec
org.junit.runners.model.TestTimedOutException: test timed out after 60000 milliseconds
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:969)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1281)
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:218)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at com.hazelcast.map.impl.query.QueryIndexMigrationTest.testIndexCleanupOnMigration(QueryIndexMigrationTest.java:183)

Users with the same issue

Once, 2 months ago
Once, 5 months ago

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