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

java/lang/StringBuilder/RacingSBThreads.java timed out in Xcomp subtest

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P4 P4
    • 26
    • 26
    • core-libs
    • master
    • x86_64
    • windows

      The following test timed out in the JDK26 CI:

      java/lang/StringBuilder/RacingSBThreads.java

      Here's a snippet from the log file:

      #section:main
      ----------messages:(9/330)----------
      command: main -Xcomp RacingSBThreads
      reason: User specified action: run main/othervm -Xcomp RacingSBThreads
      started: Fri Sep 26 11:46:02 UTC 2025
      Mode: othervm [/othervm specified]
      Process id: 26548
      Timeout information:
      --- Timeout information end.
      finished: Fri Sep 26 11:48:41 UTC 2025
      elapsed time (seconds): 159.612
      ----------configuration:(0/0)----------
      ----------System.out:(10/413)----------
      Starting READ
      pokeCycles:1000000, bounds:1972, bufChanges:4, nulls=0
      writeCycles:100000, bounds:0, sumWriter=-1474836480
      Starting INSERT
      pokeCycles:1000000, bounds:87, bufChanges:512, nulls=0
      writeCycles:100000, bounds:0, sumWriter=-1477122980
      Starting APPEND
      pokeCycles:1000000, bounds:0, bufChanges:3339, nulls=0
      Timeout signalled after 120 seconds
      writeCycles:100000, bounds:0, sumWriter=-1482090444
      ----------System.err:(1/16)----------
      STATUS:Passed.
      ----------rerun:(47/5811)*----------

      <snip>

      result: Error. Program `c:\ade\mesos\work_dir\jib-master\install\jdk-26+17-1741\windows-x64-debug.jdk\jdk-26\fastdebug\bin\java' timed out (timeout set to 120000ms, elapsed time including timeout handling was 159605ms).


      Please note that the test PASSed while the timeout handler was running.
      The test was launched with this config:

      > main -Xcomp RacingSBThreads

      and according to the test task's stdout log, we have:

      > -timeoutFactor:1

      and the end of the test's log shows:

      > timeout set to 120000ms,

      The test has these '@run' directives:

       * @run main/othervm -esa RacingSBThreads read
       * @run main/othervm -esa RacingSBThreads insert
       * @run main/othervm -esa RacingSBThreads append
       * @run main/othervm -Xcomp RacingSBThreads

      For the '-Xcomp' config, we should specify a longer timeout
      value than the default of 120. Perhaps this:

       * @run main/othervm/timeout=240 -Xcomp RacingSBThreads

      The current failure's elapsed time:

      > elapsed time (seconds): 159.612

      would fit in this new, longer timeout value.

            rriggs Roger Riggs
            dcubed Daniel Daugherty
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: