Open languitar opened 1 month ago
@languitar do you use Decoroutinator via Gradle plugin? And what’s your platform, JVM or Android?
Gradle Plugin targeting JVM
Thank you for the report. I’ll try to reproduce the issue on this week. By the way, for JVM it’s possible to install Decoroutinator at runtime without relaying on Gradle(ways 2 or 3 from https://github.com/Anamorphosee/stacktrace-decoroutinator?tab=readme-ov-file#jvm)
Thank you for the report. I’ll try to reproduce the issue on this week. By the way, for JVM it’s possible to install Decoroutinator at runtime without relaying on Gradle(ways 2 or 3 from https://github.com/Anamorphosee/stacktrace-decoroutinator?tab=readme-ov-file#jvm)
The documentation sounded like the Gradle plugin being the preferred way. Is that still true?
Dynamic agent (way 2) probably will be banned by Oracle in JDK 22. Otherwise it doesn’t matter how Decoroutinator is installed.
@languitar I tried but couldn't reproduce the issue. Maybe you can provide a sample project with the issue? Or at least provide all of your build configuration (Gradle version, applied Gradle plugins, JDK version, etc.) ?
Unfortunately, I can't share the project and I'm also unable to reproduce this in an isolated sample. I'll try to collect the build facts tomorrow when I'm back at work.
Sorry, I missed this one.
The errors only sporadically appear when running tests from within IntelliJ as far as I can tell.
Some interesting pointers that might be related:
Here's our plugin definition block:
plugins {
application
kotlin("jvm")
kotlin("plugin.serialization")
alias(libs.plugins.gradle.node)
id("tech.cariad.arche.common-repositories")
jacoco
id("jacoco-report-aggregation")
`jvm-test-suite`
id("test-report-aggregation")
alias(libs.plugins.detekt)
alias(libs.plugins.openapi.generator)
// Recover stack traces in exceptions thrown in Kotlin coroutines to see better stack traces.
alias(libs.plugins.stacktracedecoroutinator)
}
With the most recent release, things mostly work fine. But it seems that there is some (gradle build?) cache invalidation issue. Sometimes, tests can only be executed after a gradle clean. Otherwise, we see exceptions like the following one:
Sorry for not being able to provide all details here.