From ddc972a3656b1b2815e963841bb6c756bc0b11dd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jorge=20Mart=C3=ADn?= Date: Wed, 29 Jul 2026 13:28:22 +0200 Subject: [PATCH] Run `Konsist` tests sequentially It's sadly faster that way: Every time we run a test class in parallel a new JVM is started, and the `KoScope` contents can't be shared between them. This scope can take a few minutes to load, so having several instances of this happening at the same time is a terrible idea. It's actually faster to run the tests sequentially, at least locally. --- tests/konsist/build.gradle.kts | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/tests/konsist/build.gradle.kts b/tests/konsist/build.gradle.kts index 5558b1a564..ccd354db89 100644 --- a/tests/konsist/build.gradle.kts +++ b/tests/konsist/build.gradle.kts @@ -29,6 +29,11 @@ dependencies { // - Add every single module as a dependency of this one. // - Move the Konsist tests to the `app` module, but the `app` module does not need to know about Konsist. tasks.withType().configureEach { + // Disable parallel tests: every time we run a test class in parallel a new JVM is started, and the `KoScope` contents can't be shared between them. + // This scope can take 1-2min to load, so having several instances of this happening is a terrible idea. + // It's actually faster to run the tests sequentially, at least locally. + maxParallelForks = 1 + val isNotCheckTask = gradle.startParameter.taskNames.any { it.contains("check", ignoreCase = true).not() } outputs.upToDateWhen { isNotCheckTask } }