Piotr KrzemiĆski
12/27/2024, 5:48 AMe: java.lang.OutOfMemoryError: GC overhead limit exceeded
on CI (see the logs), likely in compileTestDevelopmentExecutableKotlinWasmJs
. Sometimes it passes, so I thought giving Gradle/compiler more memory (2 -> 4 GiB) would help, but it still fails. I also tried disabling WASM JS tests:
kotlin {
wasmJs {
browser {
// ...
testTask {
enabled = false
}
}
}
}
but looks like the build logic still tries to compile the tests for WASM.
1. Is it a known problem in general? I think it's a sign of something bad going on in the compiler.
2. How can I skip WASM tests entirely, so that compileTestDevelopmentExecutableKotlinWasmJs
isn't executed? I think making the test task disabled should exclude this task from the task tree?ephemient
12/27/2024, 6:22 AM-D
ephemient
12/27/2024, 6:23 AMephemient
12/27/2024, 6:27 AM./gradlew --exclude-task wasmJsBrowserTest
(-x
) actually does prevent Gradle from building unnecessary dependencies thoughPiotr KrzemiĆski
12/27/2024, 6:31 AMorg.gradle.jvmargs
, I tried adjusting -Xmx
(Gradle itself) and -Dkotlin.daemon.jvm.options="-Xmx..."
, see hereephemient
12/27/2024, 6:41 AMPiotr KrzemiĆski
12/27/2024, 6:44 AM--exclude-task wasmJsBrowserTest
did the trick, thanks! I'll stay with this workaround, coverage given by tests for Compose Desktop is good enough for this experimental project, and in the meantime I'll wait for someone from the Kotlin team to confirm what kind of problem we're seeing hereIgor Yakovlev
12/27/2024, 11:00 AMPiotr KrzemiĆski
01/02/2025, 12:21 PM