| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8227420 | 14 | Martin Doerr | P3 | Resolved | Fixed | b05 |
| JDK-8228298 | 13.0.2 | Martin Doerr | P3 | Resolved | Fixed | b01 |
| JDK-8228082 | 13.0.1 | Martin Doerr | P3 | Resolved | Fixed | master |
| JDK-8223837 | 13 | Stefan Karlsson | P4 | Resolved | Fixed | b25 |
After JDK-8223837 was pushed, we see errors in the following hotspot jtreg tests on IBM platforms (linuxppc64, linuxppc64le, linuxs390x and rs6000_64):
gc/arguments/TestCMSHeapSizeFlags.java
gc/arguments/TestG1HeapSizeFlags.java
gc/arguments/TestParallelHeapSizeFlags.java
gc/arguments/TestSerialHeapSizeFlags.java
gc/arguments/TestSoftMaxHeapSizeFlag.java
It looks like no error is observed as expected by this configuration:
expectError(new String[] { gcflag, "-Xms4M", "-XX:MinHeapSize=8M", "-version" });
as per line 138 in file test/hotspot/jtreg/gc/arguments/TestMaxHeapSizeTools.java
gc/arguments/TestCMSHeapSizeFlags.java
gc/arguments/TestG1HeapSizeFlags.java
gc/arguments/TestParallelHeapSizeFlags.java
gc/arguments/TestSerialHeapSizeFlags.java
gc/arguments/TestSoftMaxHeapSizeFlag.java
It looks like no error is observed as expected by this configuration:
expectError(new String[] { gcflag, "-Xms4M", "-XX:MinHeapSize=8M", "-version" });
as per line 138 in file test/hotspot/jtreg/gc/arguments/TestMaxHeapSizeTools.java
- backported by
-
JDK-8227420 Test failures on IBM platforms (power and s/390) after JDK-8223837
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
JDK-8223837 Add -XX:MinHeapSize flag to set the minimum heap size
-
- Resolved
-
- relates to
-
-
- Resolved
-