-
Bug
-
Resolution: Fixed
-
P4
-
13, 14
-
b27
-
x86_64
-
windows
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8226742 | 14 | Serguei Spitsyn | P4 | Resolved | Fixed | b03 |
JDK-8228246 | 13.0.2 | Serguei Spitsyn | P4 | Resolved | Fixed | b01 |
JDK-8228030 | 13.0.1 | Serguei Spitsyn | P4 | Resolved | Fixed | master |
JDK-8299929 | 11.0.19-oracle | Adithya Haradi Gopal | P4 | Resolved | Fixed | b02 |
JDK-8302641 | 11.0.19 | Goetz Lindenmaier | P4 | Resolved | Fixed | b03 |
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
```
- backported by
-
JDK-8226742 jvmti/scenarios/contention/TC04/tc04t001/TestDescription.java still fails due to wrong number of MonitorContendedEntered events
-
- Resolved
-
-
JDK-8228030 jvmti/scenarios/contention/TC04/tc04t001/TestDescription.java still fails due to wrong number of MonitorContendedEntered events
-
- Resolved
-
-
JDK-8228246 jvmti/scenarios/contention/TC04/tc04t001/TestDescription.java still fails due to wrong number of MonitorContendedEntered events
-
- Resolved
-
-
JDK-8299929 jvmti/scenarios/contention/TC04/tc04t001/TestDescription.java still fails due to wrong number of MonitorContendedEntered events
-
- Resolved
-
-
JDK-8302641 jvmti/scenarios/contention/TC04/tc04t001/TestDescription.java still fails due to wrong number of MonitorContendedEntered events
-
- Resolved
-
- clones
-
JDK-8223736 jvmti/scenarios/contention/TC04/tc04t001/TestDescription.java fails due to wrong number of MonitorContendedEntered events
-
- Resolved
-
- duplicates
-
JDK-8226638 Return of jvmti/scenarios/contention/TC04/tc04t001/TestDescription.java fails due to wrong number of MonitorContendedEntered events
-
- Closed
-
- relates to
-
JDK-8223736 jvmti/scenarios/contention/TC04/tc04t001/TestDescription.java fails due to wrong number of MonitorContendedEntered events
-
- Resolved
-
-
JDK-8226917 jvmti/scenarios/contention/TC04/tc04t001/TestDescription.java fails on jvmti->InterruptThread (JVMTI_ERROR_THREAD_NOT_ALIVE)
-
- Resolved
-