On an AArch64 machine (not sure if its really specific to this architecture or this environment/Linux build), there is a failure in the PrintNMTStatistics.java JTReg test when running with "-XX:NativeMemoryTracking=detail".
It appears that it is simply due to the test looking for the word "error" anywhere in stdout. But on this machine, we have the following as one of the modules listed:
[0x0000ffff7d28e6f8] LogOutputList::set_output_level(LogOutput*, LogLevel::type)+0x364
[0x0000ffff7db7de04] _dl_init_internal+0x100
[0x0000ffff7db8212c] dl_open_worker+0x3c0
[0x0000ffff7db7dc20] _dl_catch_error+0x6c
(malloc=2KB type=Logging #69)
This causes a failure in the test.
It appears that it is simply due to the test looking for the word "error" anywhere in stdout. But on this machine, we have the following as one of the modules listed:
[0x0000ffff7d28e6f8] LogOutputList::set_output_level(LogOutput*, LogLevel::type)+0x364
[0x0000ffff7db7de04] _dl_init_internal+0x100
[0x0000ffff7db8212c] dl_open_worker+0x3c0
[0x0000ffff7db7dc20] _dl_catch_error+0x6c
(malloc=2KB type=Logging #69)
This causes a failure in the test.