On Mon, 17 Nov 2025 20:32:52 GMT, Jonas Norlinder <[email protected]> wrote:
> Current trivial test for `TestGetTotalGcCpuTime` fails as some OSs may have a > slower update rate for the underlying CPU time thread counters than the code > anticipated, causing the test to fail which assumes that some work have been > performed and the count should be non-zero. > > Solution: All GCs we are testing are tracing GCs. Therefore, add some marking > job to inflate the GC CPU time such that we can guarantee to observe a > non-zero value. This pull request has now been integrated. Changeset: 28d94d6a Author: Jonas Norlinder <[email protected]> Committer: Kevin Walls <[email protected]> URL: https://git.openjdk.org/jdk/commit/28d94d6ab4994b844af98c5c227b40b5fb8a72e5 Stats: 12 lines in 1 file changed: 11 ins; 0 del; 1 mod 8372008: TestGetTotalGcCpuTime test failures on Windows (Some GC CPU time must have been reported) Reviewed-by: kevinw, alanb, cjplummer, dholmes ------------- PR: https://git.openjdk.org/jdk/pull/28362
