> These tests have always silently permitted a -1 return value from
> OperatingSystemMXBean CPU time methods.
>
> They need to be stricter, but occasionally Windows 2019 returns a -1 for the
> first few calls of these methods. This seems to be a Windows 2019 bug or
> peculiarity. Other Window
On Mon, 24 Mar 2025 10:13:34 GMT, Kevin Walls wrote:
> These tests have always silently permitted a -1 return value from
> OperatingSystemMXBean CPU time methods.
>
> They need to be stricter, but occasionally Windows 2019 returns a -1 for the
> first few calls of these methods. This seems to
On Mon, 24 Mar 2025 20:12:45 GMT, Leonid Mesnik wrote:
>> Kevin Walls has updated the pull request incrementally with two additional
>> commits since the last revision:
>>
>> - whitespace
>> - whitespace
>
> test/jdk/com/sun/management/OperatingSystemMXBean/GetProcessCpuLoad.java line
> 45:
On Mon, 24 Mar 2025 15:08:01 GMT, Kevin Walls wrote:
>> These tests have always silently permitted a -1 return value from
>> OperatingSystemMXBean CPU time methods.
>>
>> They need to be stricter, but occasionally Windows 2019 returns a -1 for the
>> first few calls of these methods. This see
These tests have always silently permitted a -1 return value from
OperatingSystemMXBean CPU time methods.
They need to be stricter, but occasionally Windows 2019 returns a -1 for the
first few calls of these methods. This seems to be a Windows 2019 bug or
peculiarity. Other Windows versions a
