These tests use -Xlog:all=trace which can cause excessive output that runs very slowly, especially on Windows.
A recent change,JDK-8362566, adds lots of output to -Xlog:aot+map*=trace. As a result, some of these tests are starting to timeout.
None of these tests actually require a lot of logging output. The should be fixed to use -Xlog:all=info instead.
test/hotspot/jtreg/serviceability/logging/TestBasicLogOutput.java
test/hotspot/jtreg/serviceability/logging/TestFullNames.java
test/hotspot/jtreg/serviceability/logging/TestQuotedLogOutputs.java
----------System.err:(1/16)----------
STATUS:Passed.
result: Error. Program `c:\ade\mesos\work_dir\jib-master\install\jdk-26+14-1413\windows-x64-debug.jdk\jdk-26\fastdebug\bin\java' timed out (timeout set to 120000ms, elapsed time including timeout handling was 172720ms).
Timeout handler does not show any useful information. (Suspicion is that this could be a test harness and/or infra issue as we have seen other similar timeouts.)
A recent change,
None of these tests actually require a lot of logging output. The should be fixed to use -Xlog:all=info instead.
test/hotspot/jtreg/serviceability/logging/TestBasicLogOutput.java
test/hotspot/jtreg/serviceability/logging/TestFullNames.java
test/hotspot/jtreg/serviceability/logging/TestQuotedLogOutputs.java
----------System.err:(1/16)----------
STATUS:Passed.
result: Error. Program `c:\ade\mesos\work_dir\jib-master\install\jdk-26+14-1413\windows-x64-debug.jdk\jdk-26\fastdebug\bin\java' timed out (timeout set to 120000ms, elapsed time including timeout handling was 172720ms).
Timeout handler does not show any useful information. (Suspicion is that this could be a test harness and/or infra issue as we have seen other similar timeouts.)
- relates to
-
JDK-8260555 Change the default TIMEOUT_FACTOR from 4 to 1
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk/d21e73de
-
Review(master)
openjdk/jdk/27401