Adam

> Could the failing tests be related to build cache issues, @aSemy? I think it's because Kotest now runs the tests twice: once with Java 8, and again with Java...

Hmm I think my guess was wrong. It looks like `JunitXmlReporterTest` just doesn't work on master? `./gradlew :kotest-tests:kotest-tests-junitxml:check --no-build-cache --rerun-tasks`

It looks like a test is failing, is that linked with the changes here? ``` > Task :kotest-assertions:kotest-assertions-core:jvmMaxJdkTest 2085 tests completed, 1 failed FAILURE: Executed 2085 tests in 22.9s (1...

Marked as a draft until #4298 is ready

> Could you please provide a rationale and the reasoning for the proposed API? What are practical use-cases? One reason is that there's not a clear way of how to...

I've created a new issue to take this proposal further: https://github.com/Kotlin/kotlinx.serialization/issues/2308

Could this be done at a runner level? I have a couple of suggestions for dumping the config file in the Gradle plugin. 1. make [`fun buildDokkaConfiguration()`](https://github.com/Kotlin/dokka/blob/d9c8c6c0035ad59dc0a5495f3247205bb8553295/runners/gradle-plugin/src/main/kotlin/org/jetbrains/dokka/gradle/tasks/AbstractDokkaTask.kt#L221) public, but guarded...