This is hard to reproduce, and at first I'd only seen -1 returned on the first calls to mbean.getProcessCpuLoad(). But eventually I observed a -1 at any time, including in middle of the iterations, or on the last iteration which makes the current test fail.
Should fail on Windows only if we only ever see -1 returned from getProcessCpuLoad(). Remove the "exclusiveAccess.dirs=." (JDK-8353231 adding "exclusiveAccess.dirs=." did not fix this.) ------------- Commit messages: - 8354407: Test com/sun/management/OperatingSystemMXBean/GetProcessCpuLoad.java still fails on Windows Changes: https://git.openjdk.org/jdk/pull/24961/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=24961&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8354407 Stats: 35 lines in 2 files changed: 5 ins; 24 del; 6 mod Patch: https://git.openjdk.org/jdk/pull/24961.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/24961/head:pull/24961 PR: https://git.openjdk.org/jdk/pull/24961
