JDK-8366941 : Excessive logging in serviceability tests causes timeout
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 26
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2025-09-05
  • Updated: 2025-09-25
  • Resolved: 2025-09-20
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 26
26 b17Fixed
Related Reports
Relates :  
JDK-8260555 - Change the default TIMEOUT_FACTOR from 4 to 1
Description
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.)
Comments
Changeset: d21e73de Branch: master Author: Ioi Lam <iklam@openjdk.org> Date: 2025-09-20 17:26:07 +0000 URL: https://git.openjdk.org/jdk/commit/d21e73dee3dad6332b00f5932bd266b100e9090b
20-09-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/27401 Date: 2025-09-20 01:20:17 +0000
20-09-2025
Not even sure why this test is in the serviceability directory to begin with! That aside the test does "-Xlog:all=trace" and we know from other logging tests that this is now problematic because AOT has added thousands of lines of logging at that level. So while this may be triggered by the timeout factor change we should adjust the test to generate less voluminous log data. Also worth mentioning is that we often see windows taking a very long time to write these voluminous log files.
10-09-2025
SVC triage team: This is a logging issue, sending to RT component
09-09-2025
Even though the test has no set timeout value (so default of 120s applies), on Windows we timeout at just under 3m whiles on macOS it was 6.5m. It is possible this test needs its timeout set after the change to the default TIMEOUT_FACTOR - JDK-8260555
08-09-2025