I'm not sure if this is really related to Kotest. ...

# kotest

[LeoColman]

I'm not sure if this is really related to Kotest. This piece of code I see in every kotlin project

[Attila Domokos]

Which one? The jvmTarget?

[LeoColman]

Yes

[LeoColman]

Usually targetting JVM 8 tho hahah

[Attila Domokos]

I see.

[LeoColman]

That usually means that your gradle project is targetting 1.6

[LeoColman]

While Kotest was compiled with 1.8

[LeoColman]

And for that reason you can't inline the code, as they're not compatible

[LeoColman]

Not sure if that's just that tho. But this error have a big question at StackOverflow hahah

[LeoColman]

https://stackoverflow.com/questions/48988778/cannot-inline-bytecode-built-with-jvm-target-1-8-into-bytecode-that-is-being-bui

[Attila Domokos]

This is a noob quesiton: so this setting is not going to target a specific jvm, it just gives directives to the Kotlin compiler to generate more modern (possibly Jvm 1.8 compatible) byte code.

[Mike]

As Leonardo said, Kotlintest was compiled against 1.6 before, and if you don't explicitly state a jvmTarget, then the Kotlin compiler uses 1.6.

Kotest is compiled against 1.8. Your project is still targeting 1.6. So you can't use the inline from a 1.8 on the 1.6 JVM.

What you put with withType<Test> will target only test tasks.

Hopefully that helps. Are you targetting older versions of Android, or still using JDK 1.6 for your dev? Otherwise, may as well target 1.8 as there are a number of JVM improvements that allow for 'better' bytecode generation.

[Attila Domokos]

Thank you for the info! This and reading up on it helped a ton. 💯

[sam]

Could we compile kotest to 1.6?

[sam]

I'm not sure if we're using anything from 1.8 specifically? We might be.

[Attila Domokos]

shouldThrow was the only thing complaining.

[sam]

that comes from kotest-assertions

[sam]

it might be that entire package not sure