RFR: 8366951: Test runtime/logging/StressAsyncUL.java is timing out

[David Holmes]

On Wed, 10 Sep 2025 15:36:09 GMT, Johan Sjölen <jsjolen at openjdk.org> wrote:

> Hi,
> 
> This test times out sometimes. This has been known to be caused previously by a resource-constrained execution environment. It may also be because of a race between async logging initialization and the loggers (see JDK-8362282).
> 
> This PR reduces the stress by changing the log level from `trace` to `debug`. This changes the amount of logging from 48M to 6.6M, a significant reduction.
> 
> The goal with the test was to find out if there are any bugs in the stalling mode by running it in a 'stressful' situation over a long time. The stalling mode was integrated in 2025-02-26 (see https://github.com/openjdk/jdk/pull/22770 ). I therefore believe that relaxing this test is in our interest, as it reduces the stress on our CICD infra.

Good fix. There's always a risk that "all" logging will reach a point where we get swamped with output, and that happened with AOT trace level.

-------------

Marked as reviewed by dholmes (Reviewer).

PR Review: https://git.openjdk.org/jdk/pull/27195#pullrequestreview-3207925885