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.AssertionError: Should receive message within time, but got exception: org.vertx.java.core.eventbus.ReplyException: Timed out waiting for reply
at org.junit.Assert.fail(Assert.java:88)
at org.vertx.testtools.VertxAssert.fail(VertxAssert.java:126)
at org.vertx.scala.tests.core.eventbus.EventBusTimeoutsTest$$anonfun$replyWithinTimeout$3.apply(EventBusTimeoutsTest.scala:30)
at org.vertx.scala.tests.core.eventbus.EventBusTimeoutsTest$$anonfun$replyWithinTimeout$3.apply(EventBusTimeoutsTest.scala:25)
@Narigo Maybe the timeouts should be larger to accomodate slower scenarios?
We could also create a vertx.scala.test.timefactor system or configuration property for tests and use that to multiply any timeouts we provide at test time? Then, when running in CI, we'd give it a 10 or 20 factor, and when running in our machines, give it 1. WDYT?
The text was updated successfully, but these errors were encountered:
https://vertx.ci.cloudbees.com/job/vert.x-mod-lang-scala/1439/testReport/junit/org.vertx.scala.tests.core.eventbus/EventBusTimeoutsTest/replyWithinTimeout/
@Narigo Maybe the timeouts should be larger to accomodate slower scenarios?
We could also create a
vertx.scala.test.timefactor
system or configuration property for tests and use that to multiply any timeouts we provide at test time? Then, when running in CI, we'd give it a 10 or 20 factor, and when running in our machines, give it 1. WDYT?The text was updated successfully, but these errors were encountered: