Closed Mesbah-Alam closed 2 years ago
Isn't this a test setup issue?
Do not think so, this test expects a system property vm.musl to have a value of true or false. That property is null for openj9.
It's not a system property, I don't see this property set in Hotspot, and it doesn't follow the usual conventions for system property names. It looks like a test harness property to me, we've had a number of similar problems in the past where OpenJ9 testing isn't setting a test harness property that is needed.
Example of fixing another test property for OpenJ9 @llxia https://github.com/ibmruntimes/openj9-openjdk-jdk/pull/300
@LongyuZhang could you help with this? Thanks
This failure can be reproduced on JDK 17 (hyc-grinder_20642), JDK 18 (hyc-grinder_20650), and JDK 19 (hyc-grinder_20652). Adding test property for OpenJ9 fixed these failures. PRs will be created soon.
Example of fixing another test property for OpenJ9 @llxia ibmruntimes/openj9-openjdk-jdk#300
The fixes above are merged so closing.
The issue seems to have reappeared here: https://hyc-runtimes-jenkins.swg-devops.com/job/Test_openjdk17_j9_sanity.openjdk_x86-64_mac_testList_1/84/testReport/junit/java_lang_ClassLoader_nativeLibrary_NativeLibraryTest/java/NativeLibraryTest/
Stacktrace
Error evaluating expression: invalid boolean value: `null' for expression `vm.musl'
JDK version:
14:18:12 System.getProperty('java.fullversion')=17.0.2+8
14:18:12 JRE 17 Mac OS X amd64-64-Bit Compressed References 20220209_95 (JIT enabled, AOT enabled)
14:18:12 OpenJ9 - 9dccbe076
14:18:12 OMR - dac962a28
14:18:12 JCL - 316ae6c0611 based on jdk-17.0.2+8
It doesn't "reappear", the older code stream doesn't contain the fix https://github.com/ibmruntimes/openj9-openjdk-jdk17/pull/65.
NativeLibraryTest fails with invalid boolean value:
null' for expression
vm.musl' on OpenJ9 JDK 17 while it passes on HotSpot JDK 17.Output excerpt from OpenJ9 run:
Java version:
Output excerpt from HotSpot run:
Java version: