From 85644bbbf65c4d1e0cde1f32333eb9a1edb131e6 Mon Sep 17 00:00:00 2001 From: Yahor Berdnikau Date: Wed, 12 Apr 2023 10:02:22 +0200 Subject: [PATCH] [Gradle] Don't fail TC configuration on expected OOM in test Test produces as expected OOM exception, but it should not output test logs into build logs. As TeamCity will parse them and fail because build logs contains OOM which is false-positive. --- .../kotlin/org/jetbrains/kotlin/gradle/KotlinDaemonIT.kt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/libraries/tools/kotlin-gradle-plugin-integration-tests/src/test/kotlin/org/jetbrains/kotlin/gradle/KotlinDaemonIT.kt b/libraries/tools/kotlin-gradle-plugin-integration-tests/src/test/kotlin/org/jetbrains/kotlin/gradle/KotlinDaemonIT.kt index 855b35c0055..df289c25102 100644 --- a/libraries/tools/kotlin-gradle-plugin-integration-tests/src/test/kotlin/org/jetbrains/kotlin/gradle/KotlinDaemonIT.kt +++ b/libraries/tools/kotlin-gradle-plugin-integration-tests/src/test/kotlin/org/jetbrains/kotlin/gradle/KotlinDaemonIT.kt @@ -114,8 +114,10 @@ class KotlinDaemonIT : KGPDaemonsBaseTest() { ) buildAndFail("assemble") { - assertOutputContains("Not enough memory to run compilation. Try to increase it via 'gradle.properties':") - assertOutputContains("kotlin.daemon.jvmargs=-Xmx") + // 'assertOutputContains' is not suitable here as test produces OOM which TC will false-positively treat as + // whole configuration error. So we should not output test logs into build logs. + assert(output.contains("Not enough memory to run compilation. Try to increase it via 'gradle.properties':")) + assert(output.contains("kotlin.daemon.jvmargs=-Xmx")) } } }