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

java/io/File/SetLastModified.java timed out after JDK-8229333

    Details

    • Type: Bug
    • Status: Open
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: 14
    • Fix Version/s: tbd
    • Component/s: core-libs
    • Subcomponent:
    • CPU:
      x86_64
    • OS:
      os_x

      Description

      The following test failed due to timeout in the JDK14 CI:

      java/io/File/SetLastModified.java

      Here's a snippet from the log file:

      #section:main
      ----------messages:(8/234)----------
      command: main SetLastModified
      reason: Assumed action based on file name: run main SetLastModified
      Mode: agentvm
      Agent id: 13
      Timeout refired 480 times
      Timeout information:
      --- Timeout information end.
      elapsed time (seconds): 583.431
      ----------configuration:(9/1012)----------
      Boot Layer
        class path: /mesos/work_dir/jib-master/install/java/re/jtreg/4.2/promoted/all/b14/bundles/jtreg_bin-4.2.zip/jtreg/lib/javatest.jar
                    /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 /mesos/work_dir/slaves/601ba65f-769d-4a91-8a1e-d3fc5817582d-S450/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/be7fa9c1-b023-40cf-831b-1d17de373605/runs/7246205d-0e07-469e-8ae2-a27296d2f248/testoutput/test-support/jtreg_open_test_jdk_tier2_part2/patches/java.base

      Test Layer
        class path: /mesos/work_dir/slaves/601ba65f-769d-4a91-8a1e-d3fc5817582d-S450/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/be7fa9c1-b023-40cf-831b-1d17de373605/runs/7246205d-0e07-469e-8ae2-a27296d2f248/testoutput/test-support/jtreg_open_test_jdk_tier2_part2/classes/7/java/io/File/SetLastModified.d
                    /mesos/work_dir/jib-master/install/jdk-14+23-1027/src.full/open/test/jdk/java/io/File

      ----------rerun:(28/3764)*----------

      Since this is a Tier2 failure, I would normally start this bug
      at a P3. However, this failure is very rare so starting at a P4.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                bpb Brian Burkhalter
                Reporter:
                dcubed Daniel Daugherty
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: