-
Bug
-
Resolution: Fixed
-
P4
-
6u12, 7, 8
-
b01
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8183810 | 8u161 | Alan Bateman | P4 | Resolved | Fixed | b01 |
JDK-8172039 | 8u152 | Nikita Jain | P4 | Resolved | Fixed | b01 |
JDK-8192545 | emb-8u161 | Alan Bateman | P4 | Resolved | Fixed | b01 |
TESTFAIL:java/util/concurrent/locks/ReentrantLock/CancelledLockLoops.java
The following test:
java/util/concurrent/locks/ReentrantLock/CancelledLockLoops.java
failed with message:
java.lang.Error: Completed != 2
at CancelledLockLoops$ReentrantLockLoop.test(CancelledLockLoops.java:119)
at CancelledLockLoops.main(CancelledLockLoops.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:623)
at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
at java.lang.Thread.run(Thread.java:713)
Unfortunately, the test does not print the 'completed' variable value.
It's not clear if it is a test bug or bug in the java.util.concurrent library. The bug seems to occur rarely. I was not able to reproduce it.
Possible product bugs:
- Thread.interrupt() was not delivered to a thread
- Variable named 'completed' was not shared with other threads after update and lock.unlock() operation
- other reasons??
Possible test bugs:
- one of the test threads managed to complete before the test interrupted it (at line 98)
The following test:
java/util/concurrent/locks/ReentrantLock/CancelledLockLoops.java
failed with message:
java.lang.Error: Completed != 2
at CancelledLockLoops$ReentrantLockLoop.test(CancelledLockLoops.java:119)
at CancelledLockLoops.main(CancelledLockLoops.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:623)
at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
at java.lang.Thread.run(Thread.java:713)
Unfortunately, the test does not print the 'completed' variable value.
It's not clear if it is a test bug or bug in the java.util.concurrent library. The bug seems to occur rarely. I was not able to reproduce it.
Possible product bugs:
- Thread.interrupt() was not delivered to a thread
- Variable named 'completed' was not shared with other threads after update and lock.unlock() operation
- other reasons??
Possible test bugs:
- one of the test threads managed to complete before the test interrupted it (at line 98)
- backported by
-
JDK-8172039 java/util/concurrent/locks/ReentrantLock/CancelledLockLoops.java test failed with 'Completed != 2'
- Resolved
-
JDK-8183810 java/util/concurrent/locks/ReentrantLock/CancelledLockLoops.java test failed with 'Completed != 2'
- Resolved
-
JDK-8192545 java/util/concurrent/locks/ReentrantLock/CancelledLockLoops.java test failed with 'Completed != 2'
- Resolved