New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JDK-8289146: containers/docker/TestMemoryWithCgroupV1.java fails on linux ppc64le machine with missing Memory and Swap Limit output #9319
Conversation
|
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine. It matches what we do elsewhere in container tests.
@MBaesken This change now passes all automated pre-integration checks. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 59 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, too. Shouldn't this test get fixed in 19?
Please check the new version; it still throws the exception in case the full check fails; but outputs a warning about potentially wrong / missing cgroup_enable=memory swapaccount settings of the machine . |
I adjusted the warning output, hopefully it is clearer now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/integrate |
Going to push as commit d8f4e97.
Your commit was automatically rebased without conflicts. |
On Linux ppc64le machines , the test fails with
stderr: [WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
]
exitValue = 0
java.lang.RuntimeException: 'Memory and Swap Limit is: 157286400' missing from stdout/stderr
at jdk.test.lib.process.OutputAnalyzer.shouldContain(OutputAnalyzer.java:221)
at TestMemoryWithCgroupV1.testMemoryLimitWithSwappiness(TestMemoryWithCgroupV1.java:84)
at TestMemoryWithCgroupV1.main(TestMemoryWithCgroupV1.java:61)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:578)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:312)
at java.base/java.lang.Thread.run(Thread.java:1596)
This is most likely related to "kernel does not support swap limit capabilities",
we've seen similar issues on other Linux ppc64 le machines in some tests before.
So there needs to be some special handling added to the test for the case without kernel swap limit capabilities.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/9319/head:pull/9319
$ git checkout pull/9319
Update a local copy of the PR:
$ git checkout pull/9319
$ git pull https://git.openjdk.org/jdk pull/9319/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 9319
View PR using the GUI difftool:
$ git pr show -t 9319
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/9319.diff