RFR: 8372008: TestGetTotalGcCpuTime test failures on Windows (Some GC CPU time must have been reported) [v2]
Jonas Norlinder
jnorlinder at openjdk.org
Tue Nov 18 09:00:04 UTC 2025
> 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.
Jonas Norlinder has updated the pull request incrementally with one additional commit since the last revision:
Prevent escaping
-------------
Changes:
- all: https://git.openjdk.org/jdk/pull/28362/files
- new: https://git.openjdk.org/jdk/pull/28362/files/f6d3a127..dff1c323
Webrevs:
- full: https://webrevs.openjdk.org/?repo=jdk&pr=28362&range=01
- incr: https://webrevs.openjdk.org/?repo=jdk&pr=28362&range=00-01
Stats: 7 lines in 1 file changed: 2 ins; 0 del; 5 mod
Patch: https://git.openjdk.org/jdk/pull/28362.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/28362/head:pull/28362
PR: https://git.openjdk.org/jdk/pull/28362
More information about the serviceability-dev
mailing list