https://github.com/openjdk/jdk/blame/master/test/hotspot/jtreg/compiler/loopopts/TestInfLoopNearUsePlacement.java

Apparently time measurement has shown that this test runs quite long, 17 sec. That would make it one of the slowest compiler tests.

Initial testing shows it only takes 5sec, and it has a sleep statement for 5sec, so that is expected. At least we could reduce the sleep to 1sec, seems it still compiles.

time ~/Documents/jtreg/bin/jtreg -va -s -jdk:/home/emanuel/Documents/fork5-jdk/build/linux-x64-debug/jdk/ -javaoptions:"-XX:CompileCommand=printcompilation,compiler.loopopts.TestInfLoopNearUsePlacement::test" /home/emanuel/Documents/fork5-jdk/open/test/hotspot/jtreg/compiler/loopopts/TestInfLoopNearUsePlacement.java

    287 32 % ! 3 compiler.loopopts.TestInfLoopNearUsePlacement::test @ 39 (61 bytes)
    289 33 % ! 4 compiler.loopopts.TestInfLoopNearUsePlacement::test @ 39 (61 bytes)
    296 34 ! 4 compiler.loopopts.TestInfLoopNearUsePlacement::test (61 bytes)

I wonder where the 17 sec are coming from though? Maybe just fix this, and hope we get more info later?

Do the same analysis for other tests in
test/hotspot/jtreg/compiler/loopopts/
that also have infinite-loop pattern.