This test spawns 2 forked processes, which then try to trigger a code cache OOM in FFM hotspot code. Even without `-Xcomp`, the test is already pretty slow, which increases dramatically with `-Xcomp`, since startup Java code has to be compiled 3 times, once for the main test process, and then 2 more times for forks.
There is seemingly no/very little benefit of running this test with `-Xcomp`, since the test targets hotspot, not Java code. That and the test is sensitive to code cache usage, which is changed by `-Xcomp`. So, to avoid instabilities, this PR proposes to disable the test when running with `-Xcomp`. Another option is to not forward the VM flags of the parent process to the forks, but, on the off chance that this is useful for testing some other flags, this PR chooses the approach of disabling the test when running with `-Xcomp` instead. ------------- Commit messages: - disable TestStubAllocFailure with -Xcomp Changes: https://git.openjdk.org/jdk/pull/20407/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=20407&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8324260 Stats: 1 line in 1 file changed: 1 ins; 0 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/20407.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/20407/head:pull/20407 PR: https://git.openjdk.org/jdk/pull/20407
