-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 23
-
Component/s: hotspot
-
b23
-
windows
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8363921 | 21.0.10-oracle | Shyam kishor | P4 | Resolved | Fixed | b01 |
| JDK-8367680 | 21.0.10 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
| JDK-8363923 | 17.0.18-oracle | Shyam kishor | P4 | Resolved | Fixed | b01 |
| JDK-8367686 | 17.0.18 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
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
-
-
JDK-8363923 [IR framework] Only prints stdout if exitCode is 134
-
- Resolved
-
-
JDK-8367680 [IR framework] Only prints stdout if exitCode is 134
-
- Resolved
-
-
JDK-8367686 [IR framework] Only prints stdout if exitCode is 134
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk17u-dev/fa91cf48
-
Commit(master)
openjdk/jdk21u-dev/742e7e90
-
Commit(master)
openjdk/jdk/3b271981
-
Review(master)
openjdk/jdk17u-dev/3912
-
Review(master)
openjdk/jdk21u-dev/2196
-
Review(master)
openjdk/jdk/25200