General Triage of extended.openjdk tests

[smlambert]

As we wish to enable extended.openjdk tests in weekly builds (and release builds), we must triage the various failures within them. There are any where between 70 to nearly 300 test cases failures depending on the platform, but the number of core issues that cause this number of failures seems to be small. This issue lists the set of core issues that account for most of the failures (and will allow us to temporarily disable tests while the issues are investigated and fixed):

• non-Linux platforms require machine configuration (x11 server installed) to enable jdk_awt and jdk_swing tests (see Ansible request for x11 server installed for all platforms infrastructure#1791 and Configure auto logon for macos to support non-headless tests  infrastructure#211) AND in the case that xvfb/x11 are installed on machines check that we are attempting to enable it on a machine prior to a test run (need to do this for aarch64 see: https://github.com/AdoptOpenJDK/openjdk-tests/blob/master/buildenv/jenkins/JenkinsfileBase#L562)
• on Linux platforms where x11 server is installed, many jdk_awt tests are failing with 'Incorrect focus owner' issues (see: https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk11_hs_extended.openjdk_ppc64le_linux/9/testReport/java_awt_Focus_8073453_AWTFocusTransitionTest/java/AWTFocusTransitionTest/)
• some javax/print tests require a printer to be installed (example: https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk11_hs_extended.openjdk_ppc64le_linux/9/testReport/javax_print_CheckDupFlavor/java/CheckDupFlavor/)
• compiler/jvmci tests are failing with Can't init module exports: module not found: jdk.internal.vm.ci (see: https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk11_hs_extended.openjdk_x86-64_mac/9/testReport/compiler_jvmci_meta_StableFieldTest/java/StableFieldTest/)
• some test targets contain native test lib and are failing because they need nativepath configured (Use -nativepath to specify the location of native code, see: https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk11_hs_extended.openjdk_x86-64_mac/9/testReport/tools_launcher_JliLaunchTest/java/JliLaunchTest/)
• java/beans editor tests are failing with 'java.lang.Error: could not find editor for class java.awt.Font' (see: https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk11_hs_extended.openjdk_x86-64_mac/9/testReport/java_beans_PropertyEditor_TestFontClassValue/java/TestFontClassValue/)

Individually raised issues for individually failing test classes (rather than by test target):

• extended.openjdk failure: MacOS javax.imagio all fail as no AWT Window Server #2365
• extended.openjdk failure: com/sun/jndi/dns/ConfigTests/Timeout.java.Timeout : SocketException: No route to host #2360
• extended.openjdk failure: java/rmi/registry/readTest/readTest.sh : unknown error? #2359
• extended.openjdk failure: java/nio/channels/SocketChannel/AdaptSocket.java : Incorrect number of bytes read: 15 #2358
• extended.openjdk failure: javax/imageio/AppletResourceTest.java : FontConfiguration NPE #2357
• extended.openjdk failure: javax/xml/crypto/dsig/LineFeedOnlyTest.java #2356
• extended.openjdk failure: com/sun/jndi/ldap/LdapTimeoutTest.java.LdapTimeoutTest #2355
• extended.openjdk failure: BadPluginConfigurationTest : Unrecognized system! AIX #2354
• extended.openjdk failure: AIX sun/security/krb5/auto/Unreachable timeout after 80 seconds #2353
• extended.openjdk failure: java/net/Inet6Address/B6558853.java.B6558853 #2352
• extended.openjdk failure: com/sun/jndi/ldap/DeadSSLLdapTimeoutTest.java.DeadSSLLdapTimeoutTest #2351
• extended.openjdk failure: com/sun/jndi/ldap/LdapDnsProviderTest.java.LdapDnsProviderTest #2350
• extended.openjdk failure: sun/security/krb5/auto/ReplayCacheTestProc.java.ReplayCacheTestProc #2349
• osx extended.openjdk javax/imageio/plugins/jpeg/JPEGsNotAcceleratedTest.java java.awt.HeadlessException #2327
• jdk_management_0 hang on jdk8 & jdk11 Windows 64 & 32bit #2294

[smlambert]

Fresh run of extended.openjdk on aarch64 (https://ci.adoptopenjdk.net/computer/test-packet-ubuntu1604-armv8-1/), has 364 test failures, most are java/awt test cases with 'not a focus owner' exceptions (java.lang.RuntimeException: java.lang.RuntimeException: t1 is not a focus owner), some javax/print tests that require a printer.

[smlambert]

In prep for upcoming Jan release, will exclude the 7 sub-targets that are failing and not yet triaged:

[smlambert]

FYI, @llxia @renfeiw
extended.openjdk targets on hotspot win32 all failing with

[2021-01-09T18:15:51.856Z] Unrecognized VM option 'UseCompressedOops'
[2021-01-09T18:15:51.856Z] Did you mean '(+/-)CheckCompressedOops'? Error: Could not create the Java Virtual Machine.
[2021-01-09T18:15:51.856Z] Error: A fatal exception has occurred. Program will exit.
[2021-01-09T18:15:51.856Z] failed to get JDK properties for J:\jenkins\workspace\Test_openjdk11_hs_extended.openjdk_x86-32_windows\openjdkbinary\j2sdk-image\bin\java -ea -esa -Xmx512m -XX:-UseCompressedOops; exit code 1
[2021-01-09T18:15:51.856Z] Error: failed to get JDK properties for J:\jenkins\workspace\Test_openjdk11_hs_extended.openjdk_x86-32_windows\openjdkbinary\j2sdk-image\bin\java -ea -esa -Xmx512m -XX:-UseCompressedOops; exit code 1

See https://trss.adoptopenjdk.net/allTestsInfo?buildId=5ff9fa292bad785066074bd2&limit=5&hasChildren=false

Assume related to adoptium/TKG#131 and #2146

[llxia]

Mode150/Mode650 was set the same as Mode110/Mode610 in ottawa.csv. It appears that the behavior of Mode150 and Mode110 are different on win32. I suspect Mode150 cannot run on all 32-bit. I will update ottawa.csv.

Mode650 (-XX:-UseCompressedOops) passed on win32 OpenJ9 jvm:
https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.system_x86-32_windows/109/
https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.openjdk_x86-32_windows/434/

[smlambert]

@llxia - all extended.openjdk targets are also failing against corretto trying to run Mode150 (see: https://trss.adoptopenjdk.net/allTestsInfo?buildId=5ffa04462bad7850660759cd)

[sophia-guo]

All openjdk tests with hotspot on 32 platform failed.

13:17:21  Unrecognized VM option 'UseCompressedOops'
13:17:21  Did you mean '(+/-)CheckCompressedOops'? Error: Could not create the Java Virtual Machine.
13:17:21  Error: A fatal exception has occurred. Program will exit.
13:17:21  failed to get JDK properties for J:\jenkins\workspace\Test_openjdk11_hs_extended.openjdk_x86-32_windows\openjdkbinary\j2sdk-image\bin\java -ea -esa -Xmx512m -XX:-UseCompressedOops; exit code 1
13:17:21  Error: failed to get JDK properties for J:\jenkins\workspace\Test_openjdk11_hs_extended.openjdk_x86-32_windows\openjdkbinary\j2sdk-image\bin\java -ea -esa -Xmx512m -XX:-UseCompressedOops; exit code 1

-XX:-UseCompressedOops works only for 64-bit JVMs.
https://docs.oracle.com/en/java/javase/13/docs/specs/man/java.html

[sophia-guo]

#2146 why Openjdk test targets limited to impl = hotspot need to add both mode150 and Mode650 with mode150 skipped? By default +CheckCompressedOops option is enabled, and compressed pointers are used.

[llxia]

Re #2137 (comment), For hotspot builds, Mode150 is skipped due to the platform x86-64_windows. If we use x86-64_windows_mixed, both modes will run.
For example https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_sanity.openjdk_x86-64_windows/397/

[smlambert]

Missing utilities on aarch64 machines, some tests seem to expect certain utility commands ("which" and "hostname" expected).

Example:

https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_extended.openjdk_aarch64_linux_xl/2/testReport/java_nio_file_attribute_BasicFileAttributeView_UnixSocketFile/java/UnixSocketFile/ - requires "which" to be present

https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_extended.openjdk_aarch64_linux_xl/2/testReport/sun_net_www_protocol_https_HttpsURLConnection_PostThruProxyWithAuth/java/PostThruProxyWithAuth/ and PostThruProxy.java- expects hostname to be present