JDK-8315646 : serviceability/sa/TestHeapDumpForInvokeDynamic.java fails with ZGC
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc-agent
  • Affected Version: 22
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2023-09-04
  • Updated: 2023-09-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
Relates :  
Sub Tasks
JDK-8315717 :  
JDK-8315718 :  
Description
The following test:

serviceability/sa/TestHeapDumpForInvokeDynamic.java

is failing in the JDK22 CI, since 
8311775: [TEST] duplicate verifyHeapDump in several tests

It hits the assert:

118      Asserts.assertFalse(line.matches(".*WARNING(?!.*Failed to resolve object.*constantPoolOop.*).*"));

Before 8311775, when TestHeapDumpForInvokeDynamic had its own verifyHeapDump() method, it did not check for the absence of this warning.


Comments
The 65 sightings in the JDK22 CI since 2023.09.04 are all with singlegen-zgc tasks so far. The test is already on: $ grep serviceability/sa/TestHeapDumpForInvokeDynamic.java test/hotspot/jtreg/ProblemList* test/hotspot/jtreg/ProblemList-generational-zgc.txt:serviceability/sa/TestHeapDumpForInvokeDynamic.java 8307393 generic-all so that explains why there are no genzgc failures in this latest storm.
05-09-2023

There a are a lot of bugs in the SA ZGC support. It appears this is one of them and has gone unnoticed due to the lack of proper verification of the heap dump. I think the correct approach here is to add the test to ProblemList-zgc.txt, and not to attempt to have the test ignore the warning.
04-09-2023