Openjdk-tests: Functional: JLM_Tests are failing to compile on z/OS with JDK11

Created on 3 Nov 2020  路  6Comments  路  Source: AdoptOpenJDK/openjdk-tests

Describe the bug
Functional JLM_Tests are now failing to compile on z/OS with JDK11.

Last passing job as well failing now.
Passed job has this compilation log of JLM_Tests
compile:
[2020-09-29T08:18:20.309Z] [echo] Ant version is Apache Ant(TM) version 1.9.9 compiled on February 2 2017
[2020-09-29T08:18:20.309Z] [echo] ============COMPILER SETTINGS============
[2020-09-29T08:18:20.309Z] [echo] ===fork: yes
[2020-09-29T08:18:20.309Z] [echo] ===executable: /home/jenkins/workspace/Grinder/openjdkbinary/j2sdk-image/bin/javac
[2020-09-29T08:18:20.309Z] [echo] ===debug: on
[2020-09-29T08:18:20.309Z] [echo] ===destdir: /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/bin
[2020-09-29T08:18:20.309Z] [javac] Compiling 70 source files to /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/bin
[2020-09-29T08:18:27.066Z] [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/java/lang/management/TestOperatingSystemMXBean.java:297: warning: [removal] getTotalPhysicalMemory() in ExtendedOperatingSystemMXBeanImpl has been deprecated and marked for removal
[2020-09-29T08:18:27.066Z] [javac] AssertJUnit.assertTrue(osb.getTotalPhysicalMemory() > 0);
[2020-09-29T08:18:27.066Z] [javac] ^
[2020-09-29T08:18:27.066Z] [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/management/TestOperatingSystemMXBean.java:249: warning: [removal] getTotalPhysicalMemory() in OperatingSystemMXBean has been deprecated and marked for removal
[2020-09-29T08:18:27.066Z] [javac] long totalMemory = osmxbean.getTotalPhysicalMemory();
[2020-09-29T08:18:27.066Z] [javac] ^
[2020-09-29T08:18:27.066Z] [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/management/TestOperatingSystemMXBean.java:294: warning: [removal] getProcessVirtualMemorySize() in OperatingSystemMXBean has been deprecated and marked for removal
[2020-09-29T08:18:27.066Z] [javac] long processVirtualMem = osmxbean.getProcessVirtualMemorySize();
[2020-09-29T08:18:27.066Z] [javac] ^
[2020-09-29T08:18:27.066Z] [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/management/TestOperatingSystemMXBean.java:331: warning: [removal] getProcessCpuTimeByNS() in OperatingSystemMXBean has been deprecated and marked for removal
[2020-09-29T08:18:27.066Z] [javac] processCpuTime_old = osmxbean.getProcessCpuTimeByNS();
[2020-09-29T08:18:27.066Z] [javac] ^
[2020-09-29T08:18:27.066Z] [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/management/TestOperatingSystemMXBean.java:355: warning: [removal] getProcessCpuTimeByNS() in OperatingSystemMXBean has been deprecated and marked for removal
[2020-09-29T08:18:27.066Z] [javac] processCpuTime_new = osmxbean.getProcessCpuTimeByNS();
[2020-09-29T08:18:27.066Z] [javac] ^
[2020-09-29T08:18:27.066Z] [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/management/TestOperatingSystemMXBean.java:364: warning: [removal] getProcessCpuTimeByNS() in OperatingSystemMXBean has been deprecated and marked for removal
[2020-09-29T08:18:27.066Z] [javac] processCpuTime_new = osmxbean.getProcessCpuTimeByNS();
[2020-09-29T08:18:27.066Z] [javac] ^
[2020-09-29T08:18:27.066Z] [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/softmx/SoftmxUserScenarioTest.java:52: warning: [removal] getTotalPhysicalMemory() in OperatingSystemMXBean has been deprecated and marked for removal
[2020-09-29T08:18:27.066Z] [javac] long totalPhysicalMemory = ibmOSMBean.getTotalPhysicalMemory() / ( 1024 * 1024 ) ; // get the value in MB
[2020-09-29T08:18:27.066Z] [javac] ^
[2020-09-29T08:18:27.066Z] [javac] Note: Some input files use or override a deprecated API.
[2020-09-29T08:18:27.066Z] [javac] Note: Recompile with -Xlint:deprecation for details.
[2020-09-29T08:18:27.066Z] [javac] Note: /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src_90/org/openj9/test/java/lang/management/TestThreadInfo.java uses unchecked or unsafe operations.
[2020-09-29T08:18:27.066Z] [javac] Note: Recompile with -Xlint:unchecked for details.
[2020-09-29T08:18:27.067Z] [javac] 7 warnings

Failing job log of compilation of JLM_Tests
18:28:10 [javac] Compiling 70 source files to /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/bin
18:28:21 [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/java/lang/management/TestOpenJ9DiagnosticsMXBean.java:258: error: cannot find symbol
18:28:21 [javac] String[] resetOptions = diagBean.queryDumpOptions();
18:28:21 [javac] ^
18:28:21 [javac] symbol: method queryDumpOptions()
18:28:21 [javac] location: variable diagBean of type OpenJ9DiagnosticsMXBean
18:28:21 [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/java/lang/management/TestOpenJ9DiagnosticsMXBean.java:268: error: cannot find symbol
18:28:21 [javac] String[] options = diagBean.queryDumpOptions();
18:28:21 [javac] ^
18:28:21 [javac] symbol: method queryDumpOptions()
18:28:21 [javac] location: variable diagBean of type OpenJ9DiagnosticsMXBean
18:28:21 [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/java/lang/management/TestOpenJ9DiagnosticsMXBean.java:375: error: cannot find symbol
18:28:21 [javac] String[] resetOptions = diagBeanRemote.queryDumpOptions();
18:28:21 [javac] ^
18:28:21 [javac] symbol: method queryDumpOptions()
18:28:21 [javac] location: variable diagBeanRemote of type OpenJ9DiagnosticsMXBean
18:28:21 [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/java/lang/management/TestOpenJ9DiagnosticsMXBean.java:387: error: cannot find symbol
18:28:21 [javac] String[] options = diagBeanRemote.queryDumpOptions();
18:28:21 [javac] ^
18:28:21 [javac] symbol: method queryDumpOptions()
18:28:21 [javac] location: variable diagBeanRemote of type OpenJ9DiagnosticsMXBean
18:28:21 [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/java/lang/management/TestOperatingSystemMXBean.java:297: warning: [removal] getTotalPhysicalMemory() in ExtendedOperatingSystemMXBeanImpl has been deprecated and marked for removal
18:28:21 [javac] AssertJUnit.assertTrue(osb.getTotalPhysicalMemory() > 0);
18:28:21 [javac] ^
18:28:21 [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/management/TestOperatingSystemMXBean.java:249: warning: [removal] getTotalPhysicalMemory() in OperatingSystemMXBean has been deprecated and marked for removal
18:28:21 [javac] long totalMemory = osmxbean.getTotalPhysicalMemory();
18:28:21 [javac] ^
18:28:21 [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/management/TestOperatingSystemMXBean.java:294: warning: [removal] getProcessVirtualMemorySize() in OperatingSystemMXBean has been deprecated and marked for removal
18:28:21 [javac] long processVirtualMem = osmxbean.getProcessVirtualMemorySize();
18:28:21 [javac] ^
18:28:21 [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/management/TestOperatingSystemMXBean.java:331: warning: [removal] getProcessCpuTimeByNS() in OperatingSystemMXBean has been deprecated and marked for removal
18:28:21 [javac] processCpuTime_old = osmxbean.getProcessCpuTimeByNS();
18:28:21 [javac] ^
18:28:21 [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/management/TestOperatingSystemMXBean.java:355: warning: [removal] getProcessCpuTimeByNS() in OperatingSystemMXBean has been deprecated and marked for removal
18:28:21 [javac] processCpuTime_new = osmxbean.getProcessCpuTimeByNS();
18:28:21 [javac] ^
18:28:21 [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/management/TestOperatingSystemMXBean.java:364: warning: [removal] getProcessCpuTimeByNS() in OperatingSystemMXBean has been deprecated and marked for removal
18:28:21 [javac] processCpuTime_new = osmxbean.getProcessCpuTimeByNS();
18:28:21 [javac] ^
18:28:21 [javac] /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/org/openj9/test/softmx/SoftmxUserScenarioTest.java:52: warning: [removal] getTotalPhysicalMemory() in OperatingSystemMXBean has been deprecated and marked for removal
18:28:21 [javac] long totalPhysicalMemory = ibmOSMBean.getTotalPhysicalMemory() / ( 1024 * 1024 ) ; // get the value in MB
18:28:21 [javac] ^
18:28:21 [javac] Note: /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src/j9vm/test/softmx/SoftmxRemoteTest.java uses or overrides a deprecated API.
18:28:21 [javac] Note: Recompile with -Xlint:deprecation for details.
18:28:21 [javac] Note: /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/src_90/org/openj9/test/java/lang/management/TestThreadInfo.java uses unchecked or unsafe operations.
18:28:21 [javac] Note: Recompile with -Xlint:unchecked for details.
18:28:21 [javac] 4 errors
18:28:21 [javac] 7 warnings
18:28:21
18:28:21 BUILD FAILED
18:28:21 /home/jenkins/workspace/Grinder/openjdk-tests/TKG/scripts/build_test.xml:58: The following error occurred while executing this line:
18:28:21 /home/jenkins/workspace/Grinder/openjdk-tests/functional/build.xml:52: The following error occurred while executing this line:
18:28:21 /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/build.xml:125: The following error occurred while executing this line:
18:28:21 /home/jenkins/workspace/Grinder/openjdk-tests/functional/JLM_Tests/build.xml:83: Compile failed; see the compiler error output for details.
18:28:21

To Reproduce
Re-build the below

Expected behavior
Functional tests needs to be run fine as below link

Screenshots

Additional context

bug

Most helpful comment

Closing with the plan that if an issue is still seen, it will be raised in https://github.com/eclipse/openj9/issues

All 6 comments

@psoujany - we should move this issue to where this functional JLM_Test test material lives (to the OpenJ9 repo: https://github.com/eclipse/openj9/blob/master/test/functional/JLM_Tests/playlist.xml).

Additionally, links to IBM internal Jenkins are not visible to non-IBMers. So for issues that are being tracked in the open repos, you need to think about what info you must share so that everyone can understand the problem. Include console output showing more information about where the test material fails to compile will be necessary and useful in getting to a solution, because some of us can not access the links you have shared.

@psoujany - we should move this issue to where this functional JLM_Test test material lives (to the OpenJ9 repo: https://github.com/eclipse/openj9/blob/master/test/functional/JLM_Tests/playlist.xml).

Additionally, links to IBM internal Jenkins are not visible to non-IBMers. So for issues that are being tracked in the open repos, you need to think about what info you must share so that everyone can understand the problem. Include console output showing more information about where the test material fails to compile will be necessary and useful in getting to a solution, because some of us can not access the links you have shared.

I didn't realize that this is open repo. I'll take care of it in future. I'm modifying content. Thank you the suggestion.

I'm checking on re-build steps, will update issue once I find them.

@psoujany - we should move this issue to where this functional JLM_Test test material lives (to the OpenJ9 repo: https://github.com/eclipse/openj9/blob/master/test/functional/JLM_Tests/playlist.xml).

Additionally, links to IBM internal Jenkins are not visible to non-IBMers. So for issues that are being tracked in the open repos, you need to think about what info you must share so that everyone can understand the problem. Include console output showing more information about where the test material fails to compile will be necessary and useful in getting to a solution, because some of us can not access the links you have shared.

Based on your comment raised issue under https://github.com/eclipse/openj9/issues. Is that fine to close this?

Yes, the openj9 issue should be raised in openj9 repo.

Also, the SDK used in Grinder was from months ago. Please try with the latest SDK. There is no issue in zos nightly runs.

Closing with the plan that if an issue is still seen, it will be raised in https://github.com/eclipse/openj9/issues

Was this page helpful?
0 / 5 - 0 ratings