:mega: kotlinx.coroutines 1.7.1 release is here! This is a bugfix release. Changelog: <https://githu...

# coroutines

[Dmitry Khalanskiy [JB]]

📣 kotlinx.coroutines 1.7.1 release is here!
This is a bugfix release.
Changelog: https://github.com/Kotlin/kotlinx.coroutines/releases/tag/1.7.1

[yschimke]

Nice for android test users

[yschimke]

The binary compatibility of the experimental overload of runTest is restored (#3673)

[Dmitry Khalanskiy [JB]]

We've added a default timeout to runTest. Maybe your test takes longer than 10 seconds. Try passing some other timeout value to runTest, like runTest(Duration.INFINITE) { }, or runTest(30.seconds) { }, etc.

[Javier]

I will try, thanks! if it was the case I will report it, as a feedback, a better error message indicating we can change the timeout should be great

[Dmitry Khalanskiy [JB]]

Maybe the tooling doesn't show it to you for some reason, or maybe you didn't notice it, but the error message is already there.

[Javier]

I have re-checked the stacktrace and I can't see it

[Javier]

https://github.com/JavierSegoviaCordoba/semantic-versioning-kmp/actions/runs/4975007135/jobs/8901978496

[Javier]

Is it possible to change the timeout globally? Almost all tests I have there are property tests with kotest, so they run tons of tests

[Dmitry Khalanskiy [JB]]

Seems like a tooling issue. Exceptions have some error messages, but I see none here.

Is it possible to change the timeout globally?

Not at the moment. You could do something like fun runTestNoTimeout(block: suspend TestScope.() -> Unit): Unit = runTest(Duration.INFINITE, block) and just use runTestNoTimeout throughout your codebase. If you don't like this solution, please file an issue at https://github.com/Kotlin/kotlinx.coroutines/issues with the feature request for a global setting.

[Javier]

Not sure if this can be handled in a different way by kotest tho, I will ask

[juliocbcotta]

how to know how long my tests are taking ? Because I have this same problem, but in my machine it runs in 3 seconds, do we have a way to detect that in the CI ?