On Wed, 15 Oct 2025 20:38:14 GMT, Leonid Mesnik <[email protected]> wrote:
> 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. This pull request has now been integrated. Changeset: 18165708 Author: Leonid Mesnik <[email protected]> URL: https://git.openjdk.org/jdk/commit/181657084a547457327b8657d7a8d3faa17eb1f5 Stats: 85 lines in 4 files changed: 28 ins; 0 del; 57 mod 8321687: Test vmTestbase/nsk/jvmti/scenarios/contention/TC03/tc03t002/TestDescription.java failed: JVMTI_ERROR_THREAD_NOT_ALIVE Reviewed-by: amenkov, cjplummer, sspitsyn ------------- PR: https://git.openjdk.org/jdk/pull/27831
