Hi, I've just updated to 6.1.0 and now I'm finding that all many of the tests are failing with this error:

After waiting for 10s, the test coroutine is not completing, there were active child jobs: [JobImpl{Active}@5aaff0f4, JobImpl{Active}@2822da1c]

this is still using the old testing framework. But if I switch to the new testing framework then when I do

awaitState()

no state is received and it gives an error with a 3s timeout. Is there anything obvious I'm missing?

+1 we’re seeing it often at my company, and it’s resulting in flaky tests. But we’ve also seen it on other coroutine tests (non orbit) that use the test dispatchers. We’re on latest orbit. So I wonder if its coroutines testing bug