-
Bug
-
Resolution: Fixed
-
P4
-
11, 15
-
b12
-
generic
-
linux
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8310705 | 11.0.21 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
JDK-8304775 | 11.0.20-oracle | Ivan Bereziuk | P4 | Resolved | Fixed | b01 |
JDK-8304778 | 8u381 | Ivan Bereziuk | P4 | Resolved | Fixed | b01 |
The testMemorySubsystem test in MetricsTester.java sometimes fails with messages like this :
java.lang.RuntimeException: Test failed for - memory:memory.kmem.tcp.usage_in_bytes, expected [655360], got [786432]
at jdk.test.lib.containers.cgroup.MetricsTester.fail(MetricsTester.java:207)
at jdk.test.lib.containers.cgroup.MetricsTester.testMemorySubsystem(MetricsTester.java:309)
I looked into the checking code, and looks like there is an error margin allowed in CgroupMetricsTester, which is currently 0.1 .
This might be changed to a somewhat higher value, e.g. 0.25 to make the test more robust.
java.lang.RuntimeException: Test failed for - memory:memory.kmem.tcp.usage_in_bytes, expected [655360], got [786432]
at jdk.test.lib.containers.cgroup.MetricsTester.fail(MetricsTester.java:207)
at jdk.test.lib.containers.cgroup.MetricsTester.testMemorySubsystem(MetricsTester.java:309)
I looked into the checking code, and looks like there is an error margin allowed in CgroupMetricsTester, which is currently 0.1 .
This might be changed to a somewhat higher value, e.g. 0.25 to make the test more robust.
- backported by
-
JDK-8304775 cgroup MetricsTester testMemorySubsystem fails sometimes when testing memory.kmem.tcp.usage_in_bytes
- Resolved
-
JDK-8304778 cgroup MetricsTester testMemorySubsystem fails sometimes when testing memory.kmem.tcp.usage_in_bytes
- Resolved
-
JDK-8310705 cgroup MetricsTester testMemorySubsystem fails sometimes when testing memory.kmem.tcp.usage_in_bytes
- Resolved