RFR: 8357826: Avoid running some jtreg tests when asan is configured [v3]

Matthias Baesken mbaesken at openjdk.org
Fri Jun 6 08:23:52 UTC 2025


On Thu, 5 Jun 2025 06:58:33 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:
> 
>   AOTCodeCompressedOopsTest will be handled separately

build/AbsPathsInImage.java fails with ASAN because it reports a lot of 'unwanted' paths in the binaries

java.lang.Exception: Test failed
	at AbsPathsInImage.main(AbsPathsInImage.java:122)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:565)
	at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
	at java.base/java.lang.Thread.run(Thread.java:1474)

but the test is already skipped for debug builds , so we can skip it for ASAN too, we  most likely don't want to deliver asan-enabled builds to customers.

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

PR Comment: https://git.openjdk.org/jdk/pull/25575#issuecomment-2948471473


More information about the hotspot-dev mailing list