Cloners :
|
|
Duplicate :
|
|
Relates :
|
|
Relates :
|
After JDK-8223736 fix the test still fails: Spotted in the jdk-13-1364-tier5-20190621 CI job set: https://java.se.oracle.com:10065/mdash/jobs/mach5-one-jdk-13-1364-tier5-20190621-1308-3306220/results?search=status%3Afailed%20AND%20-state%3Ainvalid https://java.se.oracle.com:11060/api/v1/results/mach5-one-jdk-13-1364-tier5-20190621-1308-3306220-tier5-rt-JFR-vmTestbase_nsk_jvmti_quick-windows-x64-debug-381-439/log windows-x64-debug: sca00ico.us.oracle.com The most interesting part of the log is: ``` Thread-1: increment event: 194 Thread-0: increment event: 195 Thread-1: increment event: 196 Thread-0: increment event: 197 Thread-1: increment event: 198 Thread-0: increment event: 198 <=== This should not happen as we already had 198 for Thread-1 The following fake exception stacktrace is for failure analysis. nsk.share.Fake_Exception_for_RULE_Creation: (tc04t001.cpp:267) enterEventsCount == 199 at nsk_lvcomplain(nsk_tools.cpp:172) # ERROR: tc04t001.cpp, 267: enterEventsCount == 199 # verified assertion is FALSE # ERROR: tc04t001.cpp, 270: Number of MonitorContendedEnter events: 198 # ERROR: tc04t001.cpp, 275: enteredEventsCount == 199 # verified assertion is FALSE # ERROR: tc04t001.cpp, 278: Number of MonitorContendedEntered events: 198 ```
|