-
Bug
-
Resolution: Fixed
-
P4
-
23
-
b23
-
windows
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8363921 | 21.0.10-oracle | Shyam kishor | P4 | Resolved | Fixed | master |
| JDK-8363923 | 17.0.18-oracle | Shyam kishor | P4 | Resolved | Fixed | master |
The IR framework only prints the stdout if exitCode == 134:
https://github.com/openjdk/jdk/blob/cbe329b90ac1488836d4852fead79aa26c082114/test/hotspot/jtreg/compiler/lib/ir_framework/driver/TestVMProcess.java#L249
This works for VM crashes/asserts on Linux but not on Windows. As a result, the jtreg log is empty making it hard to identify/filter/link the failure.
https://github.com/openjdk/jdk/blob/cbe329b90ac1488836d4852fead79aa26c082114/test/hotspot/jtreg/compiler/lib/ir_framework/driver/TestVMProcess.java#L249
This works for VM crashes/asserts on Linux but not on Windows. As a result, the jtreg log is empty making it hard to identify/filter/link the failure.
- backported by
-
JDK-8363921 [IR framework] Only prints stdout if exitCode is 134
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk/3b271981
-
Review(master)
openjdk/jdk/25200