As with timeouts, sometimes you get lucky and make it in time, and sometimes
you don't ;-)
Make sure the timeouts are reasonable, or externalise them into config and
override it for tests if you must.
Happy hakking!
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 4 November 2015 at 16:3
Then it must have been magic and not this configuration parameter that made
the tests pass :)
Thanks for your clear and fast reply!
Op woensdag 4 november 2015 16:27:32 UTC+1 schreef Konrad Malawski:
>
> As I mentioned, akka*.test.*timefactor only affects test utilities
> (expectMsg and friends)
As I mentioned, akka.test.timefactor only affects test utilities (expectMsg and
friends),
not ask nor any other Timeouts that you may have set in your application.
Time dilation is documented in the TestKit section AFAIR, and that's where it
applies, not to the entirety of Akka :-)
You can man
Hi Konrad,
Thanks for your answer. I thought the timefactor was applied to all
timeouts, for example also to the timeout used for akka.pattern.ask inside
the actor you are testing. I was using a timeout on an ask of 100ms, the
tests on the build server failed, but using akka.test.timefactor see
Hi,
I'm running into a problem when performing asynchronous integration tests
for an actor on a Jenkins build server. As suggested in the documentation
(http://doc.akka.io/docs/akka/2.3.9/scala/testing.html#Accounting_for_Slow_Test_Systems)
I am using akka.test.timefactor to increase the timeo
Hi Jan!
Thanks for asking,
This is expected behaviour though, not a bug.
The akka.test.timefactor affects only the testing utilities, like expectMsg and
it's friends.
If you want to you can apply dilation manually, based on env variables to your
timeouts (in prod code).
Thanks and happy hakkin
