Bug ID: JDK-8216181 [AOT] SA tests fail when AOT is enabled

Type: Bug
Component: hotspot
Sub-Component: compiler
Affected Version: 11,12,13,14

Priority: P3
Status: Closed
Resolution: Won't Fix

Submitted: 2019-01-04
Updated: 2022-02-07
Resolved: 2022-02-07

SA tests failed when AOT is enabled complaining about
Exception: sun.jvm.hotspot.debugger.UnalignedAddressException: eaf6a3ad
Exception: sun.jvm.hotspot.debugger.UnmappedAddressException: ...f6176616a4c1000
Exception: java.lang.RuntimeException: Stderr has output other than VM warnings
Exception: java.lang.NullPointerException

List of affected tests:
serviceability/sa/TestJhsdbJstackMixed.java
serviceability/sa/TestJhsdbJstackLock.java
serviceability/sa/JhsdbThreadInfoTest.java
serviceability/sa/ClhsdbWhere.java
serviceability/sa/ClhsdbThread.java
serviceability/sa/ClhsdbSource.java
serviceability/sa/ClhsdbPrintAs.java
serviceability/sa/ClhsdbJstack.java
serviceability/sa/ClhsdbJdis.java
serviceability/sa/ClhsdbInspect.java

So, I guess the only way is to look at them one by one. 1. serviceability/sa/TestPrintMdo.java runs LingeredApp (which doesn't really do much) and expects to have an MDO to examine. There is no guarantee that an MDO will be created and it's even more unlikely with AOT and/or tiered because the thresholds when the profiling starts are much higher. 2. serviceability/sa/TestJhsdbJstackMixed.java requires Linux, will look at it later. 3. serviceability/sa/TestJhsdbJstackLock.java 4. serviceability/sa/TestClassDump.java Actually passes on my machine. ...
15-11-2019
[~iveresov] Please look.
07-11-2019
ILW = SA tests fail with AOT, all failing tests are problem listed, no workaround (but don't execute with AOT) = HLM = P3
30-08-2019
Most of these failing SA tests have already been problem listed with AOT: http://hg.openjdk.java.net/jdk/jdk13/file/76647c08ce0c/test/hotspot/jtreg/ProblemList-aot.txt#l30 The newly failing serviceability/sa/sadebugd/DebugdConnectTest.java was added recently with JDK-8209790 and should simply be problem listed as well. I've filed JDK-8230390.
30-08-2019
The code review for 8230129 sent out by Xiaohong Gong make it sound like serviceability/sa/ClhsdbInspect.java has a test bug. If the test is expecting a direct oop pointer not to change, and therefore can't tolerate a GC, then that sounds like a test bug. The test should disable GC or use an indirect handle to reference the oop.
29-08-2019
I just got new SA failures: serviceability/sa/TestClhsdbJstackLock.java serviceability/sa/TestClassDump.java serviceability/sa/JhsdbThreadInfoTest.java serviceability/sa/ClhsdbWhere.java serviceability/sa/ClhsdbThread.java serviceability/sa/ClhsdbSource.java serviceability/sa/ClhsdbPrintAs.java serviceability/sa/ClhsdbJstack.java serviceability/sa/ClhsdbJdis.java serviceability/sa/ClhsdbAttach.java Looks like SA tests intermittently fail with AOT and as result any SA test could fail.
12-06-2019
To run tests locally do for example: > make run-test TEST="serviceability/sa/TestPrintMdo.java" TEST_VM_OPTS="-server -ea -esa" TEST_OPTS_AOT_MODULES=java.base
12-06-2019
Here the latest failures of SA test. serviceability/sa/TestPrintMdo.java JavaTest Message: Test threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: 'VirtualCallData' missing from stdout/stderr serviceability/sa/TestJhsdbJstackMixed.java JavaTest Message: Test threw exception: java.lang.RuntimeException: 'sun.jvm.hotspot.debugger.UnmappedAddressException:' found in stderr serviceability/sa/TestJhsdbJstackLock.java Error occurred during stack walking: serviceability/sa/TestClassDump.java JavaTest Message: Test threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: Expected to get exit value of [0] serviceability/sa/JhsdbThreadInfoTest.java Execution failed: `main' threw exception: java.lang.Error: Couldn't start jhsdb, attach to LingeredApp or match ThreadName serviceability/sa/ClhsdbWhere.java JavaTest Message: Test threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: 'Java Stack Trace for Common-Cleaner' missing from stdout/stderr serviceability/sa/ClhsdbThread.java JavaTest Message: Test threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: 'Finalizer' missing from stdout/stderr serviceability/sa/ClhsdbSource.java Error occurred during stack walking: serviceability/sa/ClhsdbPrintAs.java JavaTest Message: Test threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: Expected to get exit value of [0] serviceability/sa/ClhsdbJstack.java java.lang.RuntimeException: 'java.lang.ref.Finalizer\\$FinalizerThread.run' missing from stdout/stderr serviceability/sa/ClhsdbJdis.java Test ERROR java.lang.RuntimeException: Expected to get exit value of [0] serviceability/sa/ClhsdbAttach.java Test ERROR java.lang.RuntimeException: Expected to get exit value of [0]
12-06-2019