It looks like <there's an issue> with `mingw_x64`....

# kotest

[eygraber]

It looks like there's an issue with mingw_x64.

Gradle doesn't seem to be able to find the artifact for it, even though it exists.

[sam]

ok, that's probably related to a commit I made to hide mingwx on linux builds

[sam]

I'll do a 6.0.6

[Piotr Krzemiński]

@sam could you release 6.0.6? 🙏 I'm hit by the issue mentioned above, and because of various other issues, I cannot upgrade and I'm still on 6.0.0

[sam]

yes I need to do it by eow, sorry for delays

[sam]

its released now !

[eygraber]

Unfortunately it looks like there's still an issue. https://repo1.maven.org/maven2/io/kotest/kotest-assertions-core/6.0.6/kotest-assertions-core-6.0.6.module doesn't contain a variant for mingwX64ApiElements which leads to:

Execution failed for task ':jsonpath-core:compileTestKotlinMingwX64'.
> Could not resolve all files for configuration ':jsonpath-core:mingwX64TestCompileKlibraries'.
   > Could not resolve io.kotest:kotest-assertions-core:6.0.6.
     Required by:
         project ':jsonpath-core'
      > No matching variant of io.kotest:kotest-assertions-core:6.0.6 was found. The consumer was configured to find a library for use during 'kotlin-api', preferably optimized for non-jvm, as well as attribute 'org.jetbrains.kotlin.klib.packaging' with value 'non-packed', attribute 'org.jetbrains.kotlin.native.target' with value 'mingw_x64', attribute 'org.jetbrains.kotlin.platform.type' with value 'native' but:

[sam]

weird because its here https://central.sonatype.com/artifact/io.kotest/kotest-assertions-core-mingwx64/versions

[sam]

hmmm I think I see what it might be, let me try a 6.0.7 release over the top

[eygraber]

Yeah, probably something weird with the publishing plugin.

I noticed that you're using native runners to publish the corresponding artifacts; was klib cross compilation not working? I've found that publishing all the artifacts on one runner works the best for these kind of issues.

[sam]

because we publish macos / ios etc we would have to use the macos runners as the linux/windows one doesn't support them

[sam]

and github rate limits how much you can use them, so it takes forever (like hours)

[sam]

the issue here is that I tried to be cute about how/when windows builds were included to try to speed up builds, and obviously broke it for 6.0.5, I thought I had reverted it all for 6.0.6 but it looks like I missed one line, so am trying 6.0.7 shortly.

[sam]

Thanks for flagging it up again.

[sam]

https://github.com/kotest/kotest/commit/e3767727b571be713954ee28f57bd7dca3cfea4f

[eygraber]

because we publish macos / ios etc we would have to use the macos runners as the linux/windows one doesn't support them

I have to double check, but I'm pretty sure I publish macos / ios artifacts from an Ubuntu runner using cross compilation

[sam]

I was under the impression that you need a mac in order to compile to a mac. I know I can't get mac targets to work on my home linux machine. If you've got a way around that let me know as it would seriously speed up builds. The macos runners are very very slow (because they're expensive so github can't give you unlimited unthrottled minutes)

[eygraber]

Yeah that's how I'm doing it in my libraries - https://github.com/eygraber/vice/blob/master/.github/workflows/publish_release.yml#L14

This was switched on by default in Kotlin 2.2.20 - https://kotlinlang.org/docs/whatsnew2220.html#stable-cross-platform-compilation-for-kotlin-libraries

[eygraber]

It made such a huge difference when I started using this

[sam]

Unfortunately, a few limitations are still present. You still need to use a Mac machine if:
• Your library or any dependent modules have cinterop dependencies.
• You have the CocoaPods integration set up in your project.
• You need to build or test final binaries for Apple targets.

[sam]

I don't think any of that applies to us rihgt?

[sam]

(I know zero about macs, I hate apple products, so use linux exclusively 😛 )

[eygraber]

I don't think any of that applies to us rihgt?

I'm taking a quick look at the repo, but that seems to be the case

(I know zero about macs, I hate apple products, so use linux exclusively 😛 )

Same 😁

[sam]

we recently updated to kotlin 2.2.20 so we can certainly give this a try. Just today I was making a thread about how to speed up builds as they take forever.
https://kotlinlang.slack.com/archives/CSYLDDZUY/p1764506589324609

[eygraber]

This might be an issue, not fully sure

[sam]

I'm not sure we use that anymore but yeah cinterop.

[sam]

Ok ill have a play this is helpful info

[sam]

Either way 6.0.7 shorttky

[sam]

6.0.7 is out and I see mingw in the list https://repo1.maven.org/maven2/io/kotest/kotest-assertions-core/6.0.7/kotest-assertions-core-6.0.7.module

[eygraber]

That worked!

[sam]

awesome 🙂

[sam]

now we can focus on 6.1