-
Bug
-
Resolution: Fixed
-
P4
-
None
-
b16
-
linux
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8347421 | 17.0.15-oracle | Ivan Bereziuk | P4 | Resolved | Fixed | b02 |
JDK-8284513 | 17.0.4 | Severin Gehwolf | P4 | Resolved | Fixed | b01 |
JDK-8347533 | 11.0.27-oracle | Ivan Bereziuk | P4 | Resolved | Fixed | b02 |
JDK-8347704 | 8u451 | Ivan Bereziuk | P4 | Resolved | Fixed | b02 |
However the test might spuriously pass if, for some reason, the host values get returned by the OperatingSystemMXBean. Since the test always runs in a container environment this should not happen and the test should fail.
The test needs to get improved to fail if some strange swap sizes are being returned. E.g. --memory X --memory-swap X, but OperatingSystemMXBean.getTotalSwapSpaceSize > 0.
- backported by
-
JDK-8284513 [Testbug] Improve TestGetSwapSpaceSize
-
- Resolved
-
-
JDK-8347421 [Testbug] Improve TestGetSwapSpaceSize
-
- Resolved
-
-
JDK-8347533 [Testbug] Improve TestGetSwapSpaceSize
-
- Resolved
-
-
JDK-8347704 [Testbug] Improve TestGetSwapSpaceSize
-
- Resolved
-
- relates to
-
JDK-8242480 Negative value may be returned by getFreeSwapSpaceSize() in the docker
-
- Resolved
-
- links to
-
Commit openjdk/jdk17u-dev/7d3a528b
-
Commit openjdk/jdk/a7716006
-
Review openjdk/jdk17u-dev/339
-
Review openjdk/jdk/7854