RFR: 8367899: compiler/c2/gvn/TestBitCompressValueTransform.java intermittent timed out
    Damon Fenacci 
    dfenacci at openjdk.org
       
    Mon Sep 29 14:43:05 UTC 2025
    
    
  
On Mon, 29 Sep 2025 13:52:59 GMT, SendaoYan <syan at openjdk.org> wrote:
> Hi all,
> 
> After JDK-8260555 change the timeout factor from 4 to 1, make test compiler/c2/gvn/TestBitCompressValueTransform.java intermittent timed out.
> 
> There are 20 10k/20k loop count of loops in this test, this cause test need many CPU cycles to finish. If I reduce the loop count from 10k/20k to 100/200, the test failures descripted in [JDK-8350896](https://bugs.openjdk.org/browse/JDK-8350896) also reproduced when the tested jdk is jdk25u. So it seems that there no need so many loop count for these tests.
> 
> Without the proposed change, the driver action finish about 65 sencods on linux-x64, with the proposed change the driver action finish about 1.5 seconds.
Thanks @sendaoYan for fixing this. It looks ok to me but I'm just wondering: do we really need a loop for tests that don't use the counter? Shouldn't the IR framework already take care of warming up and compiling the methods?
https://github.com/openjdk/jdk/blob/9d9c0e06700116288233e3435051a1496cb64b72/test/hotspot/jtreg/compiler/lib/ir_framework/Run.java#L42-L49
-------------
PR Review: https://git.openjdk.org/jdk/pull/27548#pullrequestreview-3280234308
    
    
More information about the hotspot-compiler-dev
mailing list