-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ServiceLoaderTest.testSkipHookLoadedByDifferentClassloader failure #13534
Comments
This looks like an issue with bytebuddy. It tries to detect JVM capability using reflection: public PackageLookupStrategy run() {
try {
return new PackageLookupStrategy.ForJava9CapableVm(ClassLoader.class.getDeclaredMethod("getDefinedPackage", String.class));
} catch (Exception ignored) {
return PackageLookupStrategy.ForLegacyVm.INSTANCE;
}
} So, if there's a method named |
To my understanding they are using |
public static void main(String[] args) throws Exception {
System.err.println(ClassLoader.class.getDeclaredMethod("getDefinedPackage", String.class));
} Above code prints following on IBM Java
Detailed spec:
|
Fixed in byte-buddy 1.8.17 |
…orrectly on IBM Java 8 (Github issue raphw/byte-buddy#510).
Thanks @mdogan for reporting the byte-buddy issue and initiating the quick release of version 1.8.17. |
…orrectly on IBM Java 8 (Github issue raphw/byte-buddy#510).
…on IBM Java 8 (Github issue raphw/byte-buddy#510).
…orrectly on IBM Java 8 (Github issue raphw/byte-buddy#510).
…on IBM Java 8 (Github issue raphw/byte-buddy#510).
master (commit 4525ce5)
Failing constantly only on IBM JDK 8: https://hazelcast-l337.ci.cloudbees.com/view/Official%20Builds/job/Hazelcast-3.x-IbmJDK8/lastCompletedBuild/testReport/com.hazelcast.util/ServiceLoaderTest/testSkipHookLoadedByDifferentClassloader/
Other failures (with same stacktrace):
ServiceLoaderTest.testSkipHooksWithImplementingTheExpectedInterfaceButLoadedByDifferentClassloader
ServiceLoaderTest.testFailFastWhenHookDoesNotImplementExpectedInteface
Stacktrace:
The failure is constant, actually much earlier, but because of Jenkins jobs migration, I'm reporting it now with quite a big delay, sorry about that.
The text was updated successfully, but these errors were encountered: