Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8222417

compiler/loopopts/TestOverunrolling.java times out

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P4 P4
    • 13
    • 13
    • hotspot
    • b17
    • x86_64

      The following test has started timing out in the jdk/jdk CI:

      compiler/loopopts/TestOverunrolling.java

      so far on the MacOS X machines.

      Here's a snippet of the log file:

      #section:main
      ----------messages:(6/665)----------
      command: main -XX:+IgnoreUnrecognizedVMOptions -XX:+UnlockExperimentalVMOptions -Xcomp -XX:-TieredCompilation -XX:-UseSwitchProfiling -XX:-UseCountedLoopSafepoints -XX:LoopUnrollLimit=250 -XX:-UseG1GC -XX:+UseParallelGC compiler.loopopts.TestOverunrolling
      reason: User specified action: run main/othervm -XX:+IgnoreUnrecognizedVMOptions -XX:+UnlockExperimentalVMOptions -Xcomp -XX:-TieredCompilation -XX:-UseSwitchProfiling -XX:-UseCountedLoopSafepoints -XX:LoopUnrollLimit=250 -XX:-UseG1GC -XX:+UseParallelGC compiler.loopopts.TestOverunrolling
      Mode: othervm [/othervm specified]
      Timeout information:
      --- Timeout information end.
      elapsed time (seconds): 1252.875
      ----------configuration:(0/0)----------
      ----------System.out:(1/27)----------
      Timeout refired 1200 times
      ----------System.err:(1/15)----------
      STATUS:Passed.
      ----------rerun:(48/5101)*----------

      The test is using the default timeout value of 120 seconds/2 minutes
      and this task uses a default timeout factor of 10 so the total timeout
      value is 20 minutes.

      Notice that the test passed while the JTREG timeout handler
      was doing its work.

      Taking a quick look at CI results for this test, I see passes for
      this test in < 1 minute so I'm not sure why this test sometimes
      takes a long time.

            thartmann Tobias Hartmann
            dcubed Daniel Daugherty
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: