I've got a bunch of tests (on a very large project...

# coroutines

[Adam Brown]

I've got a bunch of tests (on a very large project) that started failing when I upgraded coroutines from 1.6.4 to 1.7.2. They are failing in weird ways that don't seem related to coroutines, but that is the only thing that changed. I also found a few that didn't need = runTest and removed it, which fixed the test! So I was curious if anyone else had had some weird issues after upgrading.

[Adam Brown]

I looked a bit at the 1.7.0 change logs and nothing jumped out to me as obviously being a problem.

[Adam Brown]

this is an Android project using Hilt, and it seems that classes unrelated to the test are getting instantiated and attempting to run. There's no obvious paths I can find in the tests to cause that, and again, this didn't happen in 1.6.4

[Paul Woitaschek]

https://github.com/Kotlin/kotlinx.coroutines/issues/3800

[Paul Woitaschek]

Here we go

[Adam Brown]

thanks, yeah I came across that one and I tried bumping up my time out, but that doesn't seem to be it

[Paul Woitaschek]

What are the weird ways then?

[Adam Brown]

they are Mockk exception (no response found) for classes that shouldn't even be instantiated for these tests.

[Adam Brown]

which of course I wouldn't expect coroutines to have anything to do with, except that these exceptions only happen when I upgrade codeines

[Adam Brown]

another wrinkle is that the tests pass when run from intelliJ, but fail when run via gradle and the command line

[Marek Kubiczek]

Are you running your test suites in parallel? Do you use mockStatic?

[Marek Kubiczek]

In other words, is it possible that you mockStatic something that other test expects not to be mocked?

[Marek Kubiczek]

Seems unrelated to the coroutines update though. 🤔

[Adam Brown]

okay I think I found something, it looks like there was some tests that were not explicitly canceling their coroutines

[Adam Brown]

did maybe the behavior of standard test dispatcher change in 1.7.0?

[alex.krupa]

Could it be related to this Mockk issue?

[Adam Brown]

that looks like exactly my problem!