> 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.)
Kevin Walls has updated the pull request incrementally with one additional commit since the last revision: No need to check ex at end, when failing ------------- Changes: - all: https://git.openjdk.org/jdk/pull/24961/files - new: https://git.openjdk.org/jdk/pull/24961/files/70cd88c3..d28b4c90 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=24961&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=24961&range=00-01 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 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
