-
Bug
-
Resolution: Not an Issue
-
P1
-
None
-
1.2.2
-
x86
-
windows_95
jdk1.2.2T on Windows95 fails JCK1.2 test
api/java_lang/Thread/sleep02/sleep0201/sleep0201.html
(sleep0201.java 1.4 98/08/31 with bug 4166410 fixed).
with following test output:
test result: Failed. sleep(100,3162) actually sleeped only 100000000 nsec
The test already assumes that clock accuracy on windows95 is 50 ms and
adds 50 ms to the period of time before and after the call to sleep(,).
So the diagnostics means that sleep(100,3162) actually sleeped some
time which is strictly less than 100000000 nsec while it should sleep at least
100003162 ns.
api/java_lang/Thread/sleep02/sleep0201/sleep0201.html
(sleep0201.java 1.4 98/08/31 with bug 4166410 fixed).
with following test output:
test result: Failed. sleep(100,3162) actually sleeped only 100000000 nsec
The test already assumes that clock accuracy on windows95 is 50 ms and
adds 50 ms to the period of time before and after the call to sleep(,).
So the diagnostics means that sleep(100,3162) actually sleeped some
time which is strictly less than 100000000 nsec while it should sleep at least
100003162 ns.
- relates to
-
JDK-4373068 Thread.sleep() does not work as expected in Solaris.
-
- Closed
-
-
JDK-4123961 (hpi) Need higher resolution System.currentTimeMillis on Win32
-
- Closed
-
-
JDK-4143354 java.lang.Thread.sleep(millis) sleeps less than specified.
-
- Closed
-