Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EventBusTimeoutsTest randomly failing, and test time factor #152

Open
galderz opened this issue Apr 17, 2014 · 0 comments
Open

EventBusTimeoutsTest randomly failing, and test time factor #152

galderz opened this issue Apr 17, 2014 · 0 comments
Assignees

Comments

@galderz
Copy link
Contributor

galderz commented Apr 17, 2014

https://vertx.ci.cloudbees.com/job/vert.x-mod-lang-scala/1439/testReport/junit/org.vertx.scala.tests.core.eventbus/EventBusTimeoutsTest/replyWithinTimeout/

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants