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

misc vmTestbase/gc/gctests timed out on a particular machine

XMLWordPrintable

    • gc
    • x86_64
    • windows

      The following two tests timed out in the JDK17 CI w/ ZGC:

      vmTestbase/gc/gctests/StringInternSyncWithGC2/TestDescription.java
      vmTestbase/gc/gctests/StringIntern/StringIntern.java

      Here's snippets from the StringInternSyncWithGC2 test log:

      #section:compile
      ----------messages:(8/388)*----------
      command: compile C:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-17+23-2075\\src.full\\open\\test\\hotspot\\jtreg\\vmTestbase\\gc\\gctests\\StringInternSyncWithGC\\StringInternSyncWithGC.java
      reason: .class file out of date or does not exist
      Mode: agentvm
      Agent id: 4
      Timeout refired 480 times
      Timeout information:
      --- Timeout information end.
      elapsed time (seconds): 3332.359
      ----------configuration:(11/941)*----------
      Boot Layer (javac runtime environment)
        class path: C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\5.1\\b01\\bundles\\jtreg_bin-5.1.zip\\jtreg\\lib\\javatest.jar
                    C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\5.1\\b01\\bundles\\jtreg_bin-5.1.zip\\jtreg\\lib\\jtreg.jar
        patch: java.base T:\\testoutput\\test-support\\jtreg_open_test_hotspot_jtreg_vmTestbase_vm_gc_misc\\patches\\java.base

      javac compilation environment
        source path: C:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-17+23-2075\\src.full\\open\\test\\hotspot\\jtreg\\vmTestbase
                     C:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-17+23-2075\\src.full\\open\\test\\lib
        class path: T:\\testoutput\\test-support\\jtreg_open_test_hotspot_jtreg_vmTestbase_vm_gc_misc\\classes\\2\\vmTestbase
                     T:\\testoutput\\test-support\\jtreg_open_test_hotspot_jtreg_vmTestbase_vm_gc_misc\\classes\\2\\test\\lib

      ----------rerun:(41/5920)*----------

      Please note that this test timed out in the *compile* phase.


      Here's a snippet from the StringIntern test's log:

      #section:main
      ----------messages:(6/261)----------
      command: main gc.gctests.StringIntern.StringIntern
      reason: User specified action: run main/othervm gc.gctests.StringIntern.StringIntern
      Mode: othervm [/othervm specified]
      Timeout information:
      --- Timeout information end.
      elapsed time (seconds): 3804.369
      ----------configuration:(0/0)----------
      ----------System.out:(39/2841)----------
      Timeout refired 480 times
      Stress time: 120 seconds
      Stress iterations factor: 1
      Stress threads factor: 1
      Stress runs factor: 1
      Max memory: 2136997888
      Sleep time: 500
      Iterations: 0
      Number of threads: 24
      Run GC thread: false
      Run mem diag thread: false
      Run forever: false
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@39bb71dd,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@3116a6b3,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@53411cd5,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@14f15a56,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@70fbfbe2,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@74dce870,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@2fa0f58a,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@319d29c2,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@1e16f0f8,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@d1a0422,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@25bebcae,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@7d3552e2,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@540dfc8c,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@96bc93b,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@59e04f74,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@e95a4e8,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@35c7c02a,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@6232f5b8,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@39f29d65,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@1a63dc57,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@11ae99a1,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@64442119,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@49709141,5,MainThreadGroup]
      Starting Thread[gc.gctests.StringIntern.StringIntern$StringGenerator@4d756d5c,5,MainThreadGroup]
      For random generator using seed: 5747435418235436495
      To re-run test with same seed value please add "-Djdk.test.lib.random.seed=5747435418235436495" to command line.
      No unexpected exceptions/errors are thrown
      ----------System.err:(1/16)----------
      STATUS:Passed.
      ----------rerun:(40/6324)*----------

      <snip>

      result: Error. Program `c:\ade\mesos\work_dir\jib-master\install\jdk-17+23-2075\windows-x64.jdk\jdk-17\bin\java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 3372493ms).


      Please note that this test passed after the timeout handler
      started running.

      The really strange part of this failure is that the timeout handler
      kicked in at 480 seconds which makes sense since the default
      timeout value is 120 seconds and the default timeoutFactor
      value is 4 so the total timeout is 480 seconds/8 minutes.

      However, the elapsed time for the test is 3804.369 seconds
      which is 63 minutes. What the heck happened that caused
      the test to take another 55 minutes after the 8 minute timeout.

            Unassigned Unassigned
            dcubed Daniel Daugherty
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: