RFR: 8372008: TestGetTotalGcCpuTime test failures on Windows (Some GC CPU time must have been reported)
duke
duke at openjdk.org
Tue Nov 18 08:34:10 UTC 2025
On Mon, 17 Nov 2025 20:32:52 GMT, Jonas Norlinder <jnorlinder at openjdk.org> 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.
@JonasNorlinder
Your change (at version f6d3a127a2583b41a851908956d7f1ed5bd434f5) is now ready to be sponsored by a Committer.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/28362#issuecomment-3546176137
More information about the serviceability-dev
mailing list