You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running on JDK 17 (and potentially some earlier versions as well), BlockHound 1.0.2.RELEASE cannot process JDK class files with a new class file version, leading to failure of several tests for the kotlinx-coroutines-debug module.
Bumping BlockHound version to 1.0.7.RELEASE solves the inability to process class files, but discovers the problem of changed JVMTI behavior (see corresponding BlockHound issue and JDK issue). Since the corresponding BlockHound issue is not solved at the moment of writing this, the following workaround needs to be added to kotlinx-coroutines-debug Gradle buildscript:
tasks.withType(Test).configureEach {
if (JavaVersion.current().isCompatibleWith(JavaVersion.VERSION_13)) {
jvmArgs += ["-XX:+AllowRedefinitionToAddDeleteMethods"]
}
}
The text was updated successfully, but these errors were encountered:
When running on JDK 17 (and potentially some earlier versions as well), BlockHound 1.0.2.RELEASE cannot process JDK class files with a new class file version, leading to failure of several tests for the
kotlinx-coroutines-debug
module.Bumping BlockHound version to 1.0.7.RELEASE solves the inability to process class files, but discovers the problem of changed JVMTI behavior (see corresponding BlockHound issue and JDK issue). Since the corresponding BlockHound issue is not solved at the moment of writing this, the following workaround needs to be added to
kotlinx-coroutines-debug
Gradle buildscript:The text was updated successfully, but these errors were encountered: