You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
java.lang.Exception: test timed out after 60000 milliseconds
at java.lang.Object.wait(Native Method)
at com.hazelcast.spi.impl.BasicInvocationFuture.pollResponse(BasicInvocationFuture.java:265)
at com.hazelcast.spi.impl.BasicInvocationFuture.waitForResponse(BasicInvocationFuture.java:216)
at com.hazelcast.spi.impl.BasicInvocationFuture.get(BasicInvocationFuture.java:193)
at com.hazelcast.spi.impl.BasicInvocationFuture.get(BasicInvocationFuture.java:173)
at com.hazelcast.concurrent.lock.ConditionImpl.doAwait(ConditionImpl.java:89)
at com.hazelcast.concurrent.lock.ConditionImpl.await(ConditionImpl.java:80)
at com.hazelcast.concurrent.lock.ConditionImpl.awaitUntil(ConditionImpl.java:110)
at com.hazelcast.concurrent.lock.ConditionTest.testAwaitUntil_whenFail(ConditionTest.java:539)
the await() method interpret negative values as infinite timeout.
This is undesirable when duration is calculated from a provided
Date - as a pause between Data creation and duration calculation
may result in a negative duration -> infinite waiting.
See hazelcast#3262 for further discussion on how to interpret negative duration.
Fixeshazelcast#4372
the await() method interpret negative values as infinite timeout.
This is undesirable when duration is calculated from a provided
Date - as a pause between Data creation and duration calculation
may result in a negative duration -> infinite waiting.
See hazelcast#3262 for further discussion on how to interpret negative duration.
Fixeshazelcast#4372
https://hazelcast-l337.ci.cloudbees.com/job/Hazelcast-3.x-nightly/com.hazelcast$hazelcast/418/testReport/junit/com.hazelcast.concurrent.lock/ConditionTest/testAwaitUntil_whenFail/
The text was updated successfully, but these errors were encountered: