RFR: 8309698: [S390X] Test hotspot/jtreg/runtime/NMT/VirtualAllocCommitMerge.java fails after JDK-8299089

Thomas Stuefe stuefe at openjdk.org
Wed Jul 10 20:07:31 UTC 2024


On Tue, 9 Jul 2024 09:41:45 GMT, mmatti-sw <duke at openjdk.org> wrote:

> On s390 the testcase "VirtualAllocCommitMerge.java" when run under Interpreter with option -Xint fails. But when run as compiled with option -Xcomp -Xbatch it Passes.

Did anyone actually analyze this problem? What is the root cause? Switching the JIT on and off at random should have no bearing on how NMT functions.

I see, looking at the test output, that it fails with 


java.lang.RuntimeException: '\[0x[0]*40dafa4000 - 0x[0]*40db004000\] committed 384KB from.*' missing from stdout/stderr


But the output is there, in the virtual mapping printout:


[0x00000040dafa4000 - 0x00000040db3a4000] reserved 4096KB for Test 

	[0x00000040dafa4000 - 0x00000040db004000] committed 384KB 


But I guess the callstack is missing? So I would like to understand why, and whats preventing the callstack from being shown, and why switching on the JIT helps?

NMT is an important component. Just disabling tests that indicate problems is not a good practice.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/20096#issuecomment-2220513228


More information about the hotspot-runtime-dev mailing list