RFR: 8273318: Some containers/docker/TestJFREvents.java configs are running out of memory

Aleksey Shipilev shade at openjdk.java.net
Tue Sep 7 08:27:36 UTC 2021


On Mon, 6 Sep 2021 10:12:33 GMT, Nick Gasson <ngasson at openjdk.org> wrote:

>> $ CONF=linux-x86_64-server-fastdebug make run-test TEST=containers/docker/TestJFREvents.java
>> 
>> STDERR:
>>  stdout: [];
>>  stderr: [WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
>> ]
>>  exitValue = 137
>> 
>> java.lang.RuntimeException: Expected to get exit value of [0]
>> 
>> at jdk.test.lib.process.OutputAnalyzer.shouldHaveExitValue(OutputAnalyzer.java:489)
>> at TestJFREvents.testContainerInfo(TestJFREvents.java:110)
>> at TestJFREvents.containerInfoTestCase(TestJFREvents.java:89)
>> at TestJFREvents.main(TestJFREvents.java:74)
>> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
>> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
>> at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:312)
>> at java.base/java.lang.Thread.run(Thread.java:833)
>> 
>> 
>> `exitValue = 137` suggests the container was killed by OOM killer. The failing configuration is with `64m`, and it is apparently too low.
>> 
>> Additional testing:
>>  - [x] Affected test now passes (5 runs out of 5 tries)
>>  - [x] `containers/docker` tests pass
>
> I've also seen this failure on some AArch64 machines and this patch fixes it for me too.

Thanks for review, @nick-arm. I wonder if @mseledts wants to take look as well?

-------------

PR: https://git.openjdk.java.net/jdk/pull/5359


More information about the hotspot-dev mailing list