The two tests
     nsk/jdi/ThreadReference/suspend/suspend001
     nsk/jdi/ObjectReference/getValue/getvalue001

fail in the same way, but both seem to have the same test logic where they
expect timeout's. I'm not sure what these tests intend to test.

tests that expect to timeout are a burden to the person running the tests.

Could these be re-written so that they don't rely on timeouts somehow?

-kto



#!/bin/sh

PATH=/export1/ohair/kto_sdk_bits/solaris-sparc/bin
LD_LIBRARY_PATH=/net/vmsqe.sfbay/export/backup/testbase/testbase_j2se_vm.v15r22_b20030905/vm/src/nsk/share/lib/sparc:/export1/ohair/kto_sdk_bits/solaris-sparc/jre/lib/sparc/client
CLASSPATH=/export1/ohair/jbuild_producer_kto_sdk_solaris_sparc_10-21T01-55_1/runnsk.sh_-jdi_4.solaris-sparc/ohair.Solaris.sparc/getvalue001_1:/net/vmsqe.sfbay/export/backup/testbase/testbase_j2se_vm.v15r22_b20030905/vm/bin/classes:/export1/ohair/kto_sdk_bits/solaris-sparc/lib/tools.jar
RAS_OPTIONS=
DISPLAY=cruella:0
SHELL=/bin/sh
HOME=/home/ohair

while [ $# -gt 0 ];
do
  if [ $1 = "-jdk" ]; then
shift 1
PATH=${1}/bin:${PATH}
shift 1
  else
if [ $1 = "-d" ]; then
shift 1
if [ $# -gt 0 ]; then
DISPLAY=$1
shift 1
else
DISPLAY=:0.0
fi
fi
  fi
done

export PATH
export LD_LIBRARY_PATH
export CLASSPATH
export RAS_OPTIONS
export DISPLAY
export SHELL
export HOME

#annotate TEST javaopt=-client
/export1/ohair/kto_sdk_bits/solaris-sparc/bin/java -client nsk.jdi.ObjectReference.getValue.getvalue001 -arch=sparc -waittime=1 -debugee.vmkind=java "-debugee.vmkeys=-client -client"
##Exit status of execution step=143
##Test timed out
##!checkExitCode


#TONGA: TIMED OUT nsk/jdi/ObjectReference/getValue/getvalue001 execute_positive