On Thu, 4 Jul 2024 10:08:30 GMT, Kevin Walls wrote:
> There are two similarly names tests.
> Recently:
> JDK-8335124: com/sun/management/ThreadMXBean/ThreadCpuTimeArray.java failed
> with CPU time out of expected range
> ...made a simple change to try and avoid noisy test failures. The same fix
On Mon, 8 Jul 2024 21:09:49 GMT, Kevin Walls wrote:
>> test/jdk/java/lang/management/ThreadMXBean/ThreadCpuTime.java line 239:
>>
>>> 237: " > ThreadUserTime = " + utime2);
>>> 238: }
>>> 239: */
>>
>> Shouldn't this be uncommented and this bit of testing restore
On Thu, 4 Jul 2024 10:08:30 GMT, Kevin Walls wrote:
> There are two similarly names tests.
> Recently:
> JDK-8335124: com/sun/management/ThreadMXBean/ThreadCpuTimeArray.java failed
> with CPU time out of expected range
> ...made a simple change to try and avoid noisy test failures. The same fix
On Mon, 8 Jul 2024 18:13:33 GMT, Chris Plummer wrote:
>> There are two similarly names tests.
>> Recently:
>> JDK-8335124: com/sun/management/ThreadMXBean/ThreadCpuTimeArray.java failed
>> with CPU time out of expected range
>> ...made a simple change to try and avoid noisy test failures. The s
On Thu, 4 Jul 2024 10:08:30 GMT, Kevin Walls wrote:
> There are two similarly names tests.
> Recently:
> JDK-8335124: com/sun/management/ThreadMXBean/ThreadCpuTimeArray.java failed
> with CPU time out of expected range
> ...made a simple change to try and avoid noisy test failures. The same fix
On Thu, 4 Jul 2024 10:08:30 GMT, Kevin Walls wrote:
> There are two similarly names tests.
> Recently:
> JDK-8335124: com/sun/management/ThreadMXBean/ThreadCpuTimeArray.java failed
> with CPU time out of expected range
> ...made a simple change to try and avoid noisy test failures. The same fix
