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

java/io/File/SetLastModified.java timed out

    XMLWordPrintable

Details

    • b17
    • x86_64
    • os_x

    Backports

      Description

        The following test failed in the JDK14 CI:

        java/io/File/SetLastModified.java

        Here's a snippet of the log file:

        #section:main
        ----------messages:(8/233)----------
        command: main SetLastModified
        reason: Assumed action based on file name: run main SetLastModified
        Mode: agentvm
        Agent id: 3
        Timeout refired 480 times
        Timeout information:
        --- Timeout information end.
        elapsed time (seconds): 568.185
        ----------configuration:(9/1003)----------
        Boot Layer
          class path: /scratch/mesos/jib-master/install/java/re/jtreg/4.2/promoted/all/b14/bundles/jtreg_bin-4.2.zip/jtreg/lib/javatest.jar
                      /scratch/mesos/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/mesos/slaves/ae206c0d-865c-4d69-a16b-c4e90bf2719f-S65/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/81826ce3-cc0e-4a69-bc16-6f61a7860075/runs/0fd9267a-01d4-4f66-a8c1-177dad9e7302/testoutput/test-support/jtreg_open_test_jdk_tier2_part2/patches/java.base

        Test Layer
          class path: /scratch/mesos/slaves/ae206c0d-865c-4d69-a16b-c4e90bf2719f-S65/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/81826ce3-cc0e-4a69-bc16-6f61a7860075/runs/0fd9267a-01d4-4f66-a8c1-177dad9e7302/testoutput/test-support/jtreg_open_test_jdk_tier2_part2/classes/0/java/io/File/SetLastModified.d
                      /scratch/mesos/jib-master/install/jdk-14+9-293/src.full/open/test/jdk/java/io/File

        ----------rerun:(27/3717)*----------


        This is a Tier2 failure so I'm starting this bug at P3.

        I have a vague memory of a recent timeout being tracked
        down to a Mac with really slow HDDs... Perhaps that's
        the case here.

        In any case, if this is a disk I/O intensive test, then perhaps
        the default timeout value should be 180 instead of 120.
        With the default timeout factor 4 that would give us 12 minutes
        instead of 8 minutes.

        Attachments

          Issue Links

            Activity

              People

                bpb Brian Burkhalter
                dcubed Daniel Daugherty
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: