RFR: 8357826: Avoid running some jtreg tests when asan is configured [v2]
Chris Plummer
cjplummer at openjdk.org
Wed Jun 4 20:12:54 UTC 2025
On Mon, 2 Jun 2025 08:07:38 GMT, Matthias Baesken <mbaesken at openjdk.org> wrote:
>> There are a couple of jtreg tests, especially in the HS area, with very special assumptions about memory layout/sizes .
>> Those fail when the address sanitizer is configured ( --enable-asan ).
>> The change adds a way to tag those tests with 'requires' so that they can be avoided easily when running jtreg tests with ASAN enabled.
>> Adjusting the tests for "pleasing" the sanitizer is not always desired (if possible for some tests it can be done later) .
>> While at it, also same is also added for ubsan .
>
> Matthias Baesken has updated the pull request incrementally with one additional commit since the last revision:
>
> TestBreakSignalThreadDump has issues with asan
serviceability/sa/ClhsdbCDSCore.java explicitly says it did not create a core file:
`# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again`
Is there a similar message for serviceability/sa/ClhsdbFindPC.java? What about all the other SA core file tests? Here's a list of all the SA core file tests:
serviceability/sa/ClhsdbCDSCore.java
serviceability/sa/ClhsdbFindPC.java#xcomp-core
serviceability/sa/ClhsdbFindPC.java#no-xcomp-core
serviceability/sa/ClhsdbPmap.java#core
serviceability/sa/ClhsdbPstack.java#core
serviceability/sa/TestJmapCore.java
serviceability/sa/TestJmapCoreMetaspace.java
-------------
PR Comment: https://git.openjdk.org/jdk/pull/25575#issuecomment-2941326294
More information about the serviceability-dev
mailing list