Test might fail with 

----------System.out:(5/399)----------
The following fake exception stacktrace is for failure analysis.
nsk.share.Fake_Exception_for_RULE_Creation: (tc03t002.cpp:144) 
jvmti->GetCurrentContendedMonitor(threadList[pThread].thread, &monitor)
at nsk_lvcomplain(nsk_tools.cpp:172)
# ERROR: tc03t002.cpp, 144: 
jvmti->GetCurrentContendedMonitor(threadList[pThread].thread, &monitor)
# jvmti error: code=15, name=JVMTI_ERROR_THREAD_NOT_ALIVE

if some of threads unexpectedly finishes during test execution. 


It might happens only for some tests that are not started and verified by 
thread. So the fix is to skip them and verify only "Debugee" threads that might 
be in the deadlock.

-------------

Commit messages:
 - 8321687: Test 
vmTestbase/nsk/jvmti/scenarios/contention/TC03/tc03t002/TestDescription.java 
failed: JVMTI_ERROR_THREAD_NOT_ALIVE

Changes: https://git.openjdk.org/jdk/pull/27831/files
  Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=27831&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8321687
  Stats: 18 lines in 1 file changed: 13 ins; 0 del; 5 mod
  Patch: https://git.openjdk.org/jdk/pull/27831.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/27831/head:pull/27831

PR: https://git.openjdk.org/jdk/pull/27831

Reply via email to