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

two keytool tests fail due to timeout

    Details

      Description

      The following tests failed in the JDK14 CI:

      sun/security/tools/keytool/GroupName.java
      sun/security/tools/keytool/EmptySubject.java

      Here's a snippet from the first log file:

      #section:main
      ----------messages:(8/222)----------
      command: main GroupName
      reason: Assumed action based on file name: run main GroupName
      Mode: agentvm
      Agent id: 6
      Timeout refired 960 times
      Timeout information:
      --- Timeout information end.
      elapsed time (seconds): 1242.936
      ----------configuration:(11/1063)----------
      Boot Layer
        class path: /scratch/opt/mach5/mesos/work_dir/jib-master/install/java/re/jtreg/4.2/promoted/all/b14/bundles/jtreg_bin-4.2.zip/jtreg/lib/javatest.jar
                    /scratch/opt/mach5/mesos/work_dir/jib-master/install/java/re/jtreg/4.2/promoted/all/b14/bundles/jtreg_bin-4.2.zip/jtreg/lib/jtreg.jar
        patch: java.base /scratch/opt/mach5/mesos/work_dir/fadc41f7-7a92-4484-b1d8-0b156d2ab1d1/testoutput/test-support/jtreg_open_test_jdk_tier2/patches/java.base

      Test Layer
        class path: /scratch/opt/mach5/mesos/work_dir/fadc41f7-7a92-4484-b1d8-0b156d2ab1d1/testoutput/test-support/jtreg_open_test_jdk_tier2/classes/1/sun/security/tools/keytool/GroupName.d
                    /scratch/opt/mach5/mesos/work_dir/jib-master/install/jdk-14+23-1024/src.full/open/test/jdk/sun/security/tools/keytool
                    /scratch/opt/mach5/mesos/work_dir/fadc41f7-7a92-4484-b1d8-0b156d2ab1d1/testoutput/test-support/jtreg_open_test_jdk_tier2/classes/1/test/lib
                    /scratch/opt/mach5/mesos/work_dir/jib-master/install/jdk-14+23-1024/src.full/open/test/lib

      ----------rerun:(31/4020)*----------

      There are a number of exceptions mentioned in the
      log file, but I think those are negative test cases.

      The test log ends with:

      [2019-11-12T01:10:14.783394Z] Waiting for completion for process 2017
      [2019-11-12T01:10:14.783607Z] Waiting for completion finished for process 2017
      Exit value: 0
      [2019-11-12T01:10:14.945310Z] Waiting for completion for process 2017
      [2019-11-12T01:10:14.945455Z] Waiting for completion finished for process 2017
      ----------System.err:(3/35)----------

      JavaTest Message: Test complete.

      result: Error. Agent error: java.lang.Exception: Agent 6 timed out with a timeout of 960 seconds; check console log for any additional details


      test result: Error. Agent error: java.lang.Exception: Agent 6 timed out with a timeout of 960 seconds; check console log for any additional details

      so I think this might be a case where the test just
      needs a little longer to run.

      The test is executed with a default timeout value of
      2 minutes/120 seconds and with a timeout factor of 8.
      So JTREG timeout handling kicked in at 16 minutes
      and the test finished at just over 20 minutes while
      timeout processing was running.

      If the timeout value for this test is bumped to
      3 minutes/180 seconds, then this test will likely
      timeout less on slower machines.


      The story with sun/security/tools/keytool/EmptySubject.java
      is similar. Here's the end of the log file:

      [2019-11-12T01:11:13.331263Z] Waiting for completion for process 2112
      [2019-11-12T01:11:13.331490Z] Waiting for completion finished for process 2112
      Exit value: 0
      [2019-11-12T01:11:13.386990Z] Waiting for completion for process 2112
      [2019-11-12T01:11:13.387142Z] Waiting for completion finished for process 2112
      ----------System.err:(3/35)----------

      JavaTest Message: Test complete.

      result: Error. Agent error: java.lang.Exception: Agent 4 timed out with a timeout of 960 seconds; check console log for any additional details


      test result: Error. Agent error: java.lang.Exception: Agent 4 timed out with a timeout of 960 seconds; check console log for any additional details

        Attachments

          Activity

            People

            • Assignee:
              rhalade Rajan Halade
              Reporter:
              dcubed Daniel Daugherty
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: