-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b05
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8366168 | 25.0.2 | Abhishek N | P4 | Resolved | Fixed | master |
| JDK-8366288 | 21.0.10-oracle | Abhishek N | P4 | Resolved | Fixed | master |
A lack of sufficient testing exists in the current test program for the logging functionality introduced in JDK-8301627. This functionality logs a message and stack trace when System.exit(status) or Runtime.exit(status) is invoked.
The current test cases do not sufficiently confirm:
- Scenarios where logging may not occur due to certain logging levels being configured (e.g., ALL, TRACE, WARNING, etc.).
- Validation of the stack trace to ensure it includes critical frames related to the invocation of System.exit or Runtime.exit.
The current test cases do not sufficiently confirm:
- Scenarios where logging may not occur due to certain logging levels being configured (e.g., ALL, TRACE, WARNING, etc.).
- Validation of the stack trace to ensure it includes critical frames related to the invocation of System.exit or Runtime.exit.
- backported by
-
JDK-8366168 Improve java/lang/RuntimeTests/RuntimeExitLogTest.java
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk25u/0e189759
-
Commit(master)
openjdk/jdk/1926aeb1
-
Review(master)
openjdk/jdk25u/96
-
Review(master)
openjdk/jdk/24050
(1 links to)