openjdk: add hotspot_vmTestbase_vm_compiler target

[zzambers]

Adds hotspot vmTestbase_vm_compiler target to openjdk tests.

(VM testbase tests were opensourced in jdk11, but so far are missing in aqa-tests.)

Testing:
jdk11 - RESULTS

• arm_linux, x86-64_linux, aarch64_linux, ppc64le_linux, x86-64_windows, x86-32_windows, ppc64_aix: OK
• s390x_linux, x86-64_mac - 1 failure (GraphApplet.java)

jdk17 - RESULTS

• x86-64_linux, aarch64_linux, s390x_linux, x86-64_windows, x86-64_mac: OK
• x86-64_mac - 1 failure (GraphApplet.java)

jdk21 - RESULTS

• aarch64_linux, s390x_linux, x86-64_windows, ppc64_aix: OK
• x86-64_mac - 1 failure (GraphApplet.java)
• x86-64_linux - infra error on (jdk21 does not work on rhel-6 due to missing glibc symbols)

jdk25 - RESULTS

• x86-64_linux, x86-64_windows, riscv64_linux: OK
• x86-64_windows, x86-64_mac - 1 failure (GraphApplet.java)
• aarch64_linux - infra error (?), no tests seem to have been ran

Tests summary:

• apart from infra issues, there seems to be just 1 somewhat unstable test (GraphApplet.java) , which seems to always fail on Mac, and randomly on other OSes

[zzambers]

Failing test (GraphApplet.java) seems to be caused by system desktop session/gui configuration issues.
Test mostly fails with this exception:

java.awt.HeadlessException: The application does not have desktop access, but this program performed an operation which requires it. 

otherwise, There is one instance of this exception on Mac

Execution failed: `main' threw exception: java.lang.UnsatisfiedLinkError: /Users/jenkins/workspace/Grinder/jdkbinary/j2sdk-image/Contents/Home/lib/libawt.dylib: dlopen(/Users/jenkins/workspace/Grinder/jdkbinary/j2sdk-image/Contents/Home/lib/libawt.dylib, 1): Library not loaded: /System/Library/Frameworks/JavaRuntimeSupport.framework/Versions/A/JavaRuntimeSupport Referenced from: /Users/jenkins/workspace/Grinder/jdkbinary/j2sdk-image/Contents/Home/lib/libawt.dylib Reason: image not found    

And one instance of this on linux/s390x

...
Caused by: java.lang.RuntimeException: Fontconfig head is null, check your fonts or fonts configuration
	at java.desktop/sun.awt.FontConfiguration.getVersion(FontConfiguration.java:1271)
	at java.desktop/sun.awt.FontConfiguration.readFontConfigFile(FontConfiguration.java:225)
	at java.desktop/sun.awt.FontConfiguration.init(FontConfiguration.java:107)
	at java.desktop/sun.awt.X11FontManager.createFontConfiguration(X11FontManager.java:719)
	at java.desktop/sun.font.SunFontManager$2.run(SunFontManager.java:379)
	at java.base/java.security.AccessController.doPrivileged(Native Method)
	at java.desktop/sun.font.SunFontManager.<init>(SunFontManager.java:324)
	at java.desktop/sun.awt.FcFontManager.<init>(FcFontManager.java:35)
	at java.desktop/sun.awt.X11FontManager.<init>(X11FontManager.java:56)
	... 17 more

In case of mac gui tests are probably not expected to work (see infra issue). Other ones seem like random gui configuration issue on some test systems.

[zzambers]

I have excluded vmTestbase/jit/misctests/fpustack/GraphApplet.java on macosx, as gui tests do not seem supported there yet. It is excluded in LTS releases up to jdk 25. On jdk 26+ exclude is not necessary, since test was removed as part of JDK-8359053.

[zzambers]

Tried to reschedule:

• jdk11 / s390x_linux / vmTestbase/jit/misctests/fpustack/GraphApplet: OK
• jdk25 / x86-64_windows / vmTestbase/jit/misctests/fpustack/GraphApplet: FAIL, FAIL

both windows failures are again:

Execution failed: `main' threw exception: java.awt.HeadlessException: The application does not have desktop access, but this program performed an operation which requires it.

seems like system configuration issue. However windows runs of other jdks passed on windows (so seems to work sometimes).
Should I exclude this test everywhere?

[smlambert]

Hi @zzambers - Is there an open issue this PR is associated with? (same question for #6619 or #6646)

Can you confirm there is no duplicate testcases in this test target (hotspot_vmTestbase_vm_compiler, or hotspot_vmTestbase_vm_gc or hotspot_vmTestbase_vm_defmeth) that are included in other targets?

There are duplicate testcases in other targets (see #6565) which will need to be rectified.

[zzambers]

Hi @smlambert,
I have not created issues for these, just PRs.

There is no overlap between vmtestbase tests and other hotspot groups (except for hotspot_all, which runs everything.) vmTestbase live in their own directory vmTestbase.

Also there should be no overlap between these vmTestbase groups, as subdirectories are different.

vmTestbase_vm_gc

vmTestbase/vm/gc
vmTestbase/gc

vmTestbase_vm_compiler

vmTestbase/vm/compiler/
vmTestbase/jit/
vmTestbase/vm/jit

vmTestbase_vm_defmeth

vmTestbase/vm/runtime/defmeth