-
Bug
-
Resolution: Fixed
-
P4
-
17, 18
-
b10
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8283016 | 17.0.4-oracle | PAWAN CHAWDHARY | P4 | Resolved | Fixed | b01 |
JDK-8283157 | 17.0.4 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
runtime/logging/MonitorMismatchTest.java, ClassInitializationTest.java, ClassResolutionTest.java, LoaderConstraintsTest.java and CondyIndyTest.java tests spawn a new JVMs but don't check their exit code.
- backported by
-
JDK-8283016 some hotspot runtime/logging tests don't check exit code
-
- Resolved
-
-
JDK-8283157 some hotspot runtime/logging tests don't check exit code
-
- Resolved
-
- relates to
-
JDK-8272169 runtime/logging/LoaderConstraintsTest.java doesn't build test.Empty
-
- Resolved
-
- links to
-
Commit openjdk/jdk17u-dev/88216d84
-
Commit openjdk/jdk/3b899ef7
-
Review openjdk/jdk17u-dev/247
-
Review openjdk/jdk/5062
(2 links to)