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 metanet
, 1 year ago
test timed out after 120000 milliseconds
via GitHub by hasancelik
, 2 years ago
test timed out after 300000 milliseconds
via GitHub by bilalyasar
, 2 years ago
via GitHub by Scottmitch
, 2 years ago
via GitHub by hasancelik
, 2 years ago
test timed out after 300000 milliseconds
org.junit.runners.model.TestTimedOutException: test timed out after 60000 milliseconds at java.lang.Thread.sleep(Native Method) at java.util.concurrent.TimeUnit.sleep(TimeUnit.java:372) at com.hazelcast.test.HazelcastTestSupport.sleepMillis(HazelcastTestSupport.java:297) at com.hazelcast.test.HazelcastTestSupport.assertTrueEventually(HazelcastTestSupport.java:909) at com.hazelcast.test.HazelcastTestSupport.waitAllForSafeState(HazelcastTestSupport.java:614) at com.hazelcast.test.HazelcastTestSupport.waitAllForSafeState(HazelcastTestSupport.java:610) at com.hazelcast.map.impl.query.QueryIndexMigrationTest.testQueryWithIndexDuringJoin(QueryIndexMigrationTest.java:223)