- 
    Bug 
- 
    Resolution: Fixed
- 
     P4 P4
- 
    14, 16
- 
        b14
- 
        x86_64
- 
        os_x, windows
                    The following test failed due to timeout in the JDK14 CI:
vmTestbase/vm/mlvm/mixed/stress/java/findDeadlock/TestDescription.java
#section:main
----------messages:(6/289)----------
command: main vm.mlvm.mixed.stress.java.findDeadlock.INDIFY_Test
reason: User specified action: run main/othervm vm.mlvm.mixed.stress.java.findDeadlock.INDIFY_Test
Mode: othervm [/othervm specified]
Timeout information:
--- Timeout information end.
elapsed time (seconds): 1452.524
----------configuration:(0/0)----------
----------System.out:(2/54)----------
Timeout refired 1200 times
### TRACE 1: TEST PASSED
----------System.err:(0/0)----------
I don't know this test so I don't know if the
"TRACE 1: TEST PASSED" is for one subtest or
if it is for the entire test.
vmTestbase/vm/mlvm/mixed/stress/java/findDeadlock/TestDescription.java
#section:main
----------messages:(6/289)----------
command: main vm.mlvm.mixed.stress.java.findDeadlock.INDIFY_Test
reason: User specified action: run main/othervm vm.mlvm.mixed.stress.java.findDeadlock.INDIFY_Test
Mode: othervm [/othervm specified]
Timeout information:
--- Timeout information end.
elapsed time (seconds): 1452.524
----------configuration:(0/0)----------
----------System.out:(2/54)----------
Timeout refired 1200 times
### TRACE 1: TEST PASSED
----------System.err:(0/0)----------
I don't know this test so I don't know if the
"TRACE 1: TEST PASSED" is for one subtest or
if it is for the entire test.
- relates to
- 
                    JDK-8208278 [mlvm] [TESTBUG] vm.mlvm.mixed.stress.java.findDeadlock.INDIFY_Test Deadlocked threads are not always detected -           
- Resolved
 
-         
- 
                    JDK-8259242 Remove ProtectionDomainSet_lock -           
- Resolved
 
-         
- 
                    JDK-8301461 vmTestbase/vm/mlvm/mixed/stress/java/findDeadlock/TestDescription.java fails with timeout -           
- Open
 
-