Name: vpR10197 Date: 12/15/2003


----------------------------------------------------------
Test : nsk/jdi/ThreadReference/status/status005
TestBase : testbase_nsk
VM : Client, Server
Mode : all
Platform : all
JDK : 1.5.0-b30
----------------------------------------------------------

Error message:
# ERROR: debugger FAILURE > CHECK1 FAILED
# ERROR: debugger FAILURE > ThreadReference.status() returned unexpected status THREAD_STATUS_UNKNOWN for unsuspended threadWaitingInfinitely
# ERROR: debugger FAILURE > Expected status : THREAD_STATUS_WAIT
# ERROR: debugger FAILURE > CHECK2 FAILED
# ERROR: debugger FAILURE > ThreadReference.status() returned unexpected status THREAD_STATUS_UNKNOWN for suspended threadWaitingInfinitely
# ERROR: debugger FAILURE > Expected status : THREAD_STATUS_WAIT
# ERROR: debugger FAILURE > CHECK3 FAILED
# ERROR: debugger FAILURE > ThreadReference.status() returned unexpected status THREAD_STATUS_UNKNOWN for unsuspended threadWaitingLong
# ERROR: debugger FAILURE > Expected status : THREAD_STATUS_WAIT
# ERROR: debugger FAILURE > CHECK4 FAILED
# ERROR: debugger FAILURE > ThreadReference.status() returned unexpected status THREAD_STATUS_UNKNOWN for suspended threadWaitingLong
# ERROR: debugger FAILURE > Expected status : THREAD_STATUS_WAIT

The test checks if the method returns ThreadReference.THREAD_STATUS_WAIT
status for debuggee's thread when it performs Object.wait() call or
Object.wait(long) call.

This failures is observed with b30, but it is not reproduced with b31.

The test also fails in the latest nightly runs, please see JDI_QUICKLOOK failures:
    http://vmsqe.sfbay.sun.com/nightly/mantis/DTWS/results/12-12-03/report.html

This test is available since release 25 of testbase.

======================================================================

###@###.### 2003-12-18
This bug also causes this test to fail:
   nsk/jdi/ObjectReference/waitingThreads/waitingthreads004

###@###.### 2003-12-18

The failure mode of status005 during Tiger-B32 is a little different:

#debugger > ObjectReference.waitingThreads() contains expected reference to threadWaitingInfinitely
#debugger > CHECK1 PASSED
#debugger > ThreadReference.status() returned expected status THREAD_STATUS_WAIT for unsuspended threadWaitingInfinitely
#debugger > CHECK2 PASSED
#debugger > ThreadReference.status() returned expected status THREAD_STATUS_WAIT for suspended threadWaitingInfinitely
#debugger > ObjectReference.waitingThreads() contains expected reference to threadWaitingLong
## ERROR: debugger FAILURE > CHECK3 FAILED
## ERROR: debugger FAILURE > ThreadReference.status() returned unexpected status THREAD_STATUS_UNKNOWN for unsuspended threadWaitingLong
## ERROR: debugger FAILURE > Expected status : THREAD_STATUS_WAIT
## ERROR: debugger FAILURE > CHECK4 FAILED
## ERROR: debugger FAILURE > ThreadReference.status() returned unexpected status THREAD_STATUS_UNKNOWN for suspended threadWaitingLong
## ERROR: debugger FAILURE > Expected status : THREAD_STATUS_WAIT


===============================
###@###.### 2004-02-02
===============================
It looks like following tests (winia64 only)also failed with the same bug.
http://vmsqe.sfbay/pit/tiger/DTWS/results/20040129150720.azeem.baseline/ServerVM/64BITWIN-IA64/mixed/VM/VM_QUICKLOOK1-29-PIT-VM-ServerVM-mixed-64BITWIN-IA64-en-2004-02-02-11-57-56-0390/analysis.html

nsk/jdi/ObjectReference/waitingThreads/waitingthreads002 execute_positive waitingthreads002 quick,nsk,jpda,jdi
nsk/jdi/ObjectReference/waitingThreads/waitingthreads003 execute_positive waitingthreads003 quick,nsk,jpda,jdi
nsk/jdi/ThreadReference/status/status004 execute_positive status004 quick,nsk,jpda,jdi
nsk/jdi/ThreadReference/status/status006 execute_positive status006 quick,nsk,jpda,jdi
nsk/jdi/ThreadReference/status/status007 execute_positive status007 quick,nsk,jpda,jdi