John O'Reilly07/27/2021, 4:49 PM
in 1.5.1.....we're updating a client here from a 1.4.x version and have isolated issue we're seeing to update from 1.5.0 to 1.5.1.....we have unit tests that are using
after that update....digging deeper to try and narrow in on what's changed but just in case anyone encountered this before....
IllegalStateException: This job has not completed yet
Javier07/27/2021, 4:59 PM
John O'Reilly07/27/2021, 5:02 PM
Aleksei Tirman [JB]07/28/2021, 10:04 AM
John O'Reilly07/28/2021, 10:05 AM
for unit tests that use
Aleksei Tirman [JB]07/28/2021, 10:07 AM
John O'Reilly07/28/2021, 10:25 AM
e5l07/28/2021, 10:48 AM
method there. Could you provide the whole code snippet to figure it out?
John O'Reilly07/28/2021, 10:51 AM
and then testing one of our classes that in turn is using another class that uses
. Do you know of any examples/samples etc that are able to use
that I can maybe compare to?
e5l07/28/2021, 10:52 AM
John O'Reilly07/28/2021, 10:53 AM
Aleksei Tirman [JB]07/28/2021, 10:53 AM
John O'Reilly07/28/2021, 11:02 AM
when constructing the class under test
e5l07/28/2021, 11:03 AM
When switched to lazy execution using pauseDispatcher any coroutines started via launch or async will not execute until a call to DelayController.runCurrent or the virtual clock-time has been advanced via one of the methods on DelayController.
John O'Reilly07/28/2021, 11:12 AM
in these particular tests right now