Did something change between RC2 and release in th...
# eap
z
Did something change between RC2 and release in the kotlin-bom around tests? RC2 was passing for us on CI, but with the final release I see some esoteric gradle conflicts around the kotlin test libraries. Lmk if I should file a bug
šŸ‘€ 1
i
cc @tapchicoma
t
RC2 release should be the similar to final release. And I don't see any changes in bom file. Please open an issue with repro
z
Will see if I can get a public repro going
Were any of these artifacts folded due to JDK 8 like the stdlib artifacts were?
t
afaik no
z
Hmmm strange. Iā€™ll keep digging
t
I've checked
.modules
files content between the releases and only difference between them is capabilities order šŸ¤”
z
super weird, when I output dependencies on CI, I see junit5 coming in from kotlin-test
Copy code
|    +--- project :libraries:foundation:test-commons
|    |    +--- org.ow2.asm:asm-bom:9.4 (*)
|    |    +--- org.jetbrains.kotlinx:kotlinx-coroutines-bom:1.6.4 (*)
|    |    +--- com.google.firebase:firebase-bom:31.1.1 (*)
|    |    +--- org.jetbrains.kotlin:kotlin-bom:1.8.0 (*)
|    |    +--- com.squareup.okhttp3:okhttp-bom:5.0.0-alpha.10 (*)
|    |    +--- com.squareup.okio:okio-bom:3.3.0 (*)
|    |    +--- com.squareup.wire:wire-bom:4.4.3 (*)
|    |    +--- project :tooling:slack-platform (*)
|    |    +--- junit:junit:4.13.2 (*)
|    |    +--- org.jetbrains.kotlin:kotlin-test:1.8.0
|    |    |    +--- org.jetbrains.kotlin:kotlin-stdlib:1.8.0 (*)
|    |    |    \--- org.jetbrains.kotlin:kotlin-test-junit5:1.8.0 FAILED
Iā€™m entirely unable to reproduce this locally though
so somehow on CI,
junit5RuntimeVariant
is being selected as the capability
I wonder if thereā€™s a gradle plugin sneakily turning on
useJUnitPlatform()
in test tasks
bonus bit to close this out - the reason I didnā€™t hit this on CI previously was because I was doing most of my initial testing prior to this on github actions, and our final ā€œmainā€ CI is on buildkite. Hence why I didnā€™t see it before. Will include that in testing future EAPs šŸ˜