-
Notifications
You must be signed in to change notification settings - Fork 722
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
AssertionError with testOSMXBeanLocal #12038
Comments
The failure was reproduced in a Grinder run on build-docker-ubuntu1804-armv8-3 https://ci.adoptopenjdk.net/job/Grinder/7219/:
I cannot reproduce the failure on my machine using the binary OpenJDK11U-jdk_aarch64_linux_openj9_2021-02-23-18-05.tar.gz from https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-aarch64-openj9/673/. Environment-dependent problem? |
A run on test-alibaba-ubuntu1804-armv8-1 was successful. |
https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_extended.functional_aarch64_linux/117/ on build-docker-fedora33-armv8-5 was a successful run, but that was before the mixed refs build became the default. |
Probably worth us testing a standalone java app that calls those two system calls and test that on various systems - unfortunatley the test isn't printing the values it has receieved so can't be debugged directly from that output. (Are those J9-specific methods being called?) The question may become "What should it return"? particularly in the case where a docker image is capped on a host system. |
The location of the assertion is https://github.com/eclipse/openj9/blob/4913c6500c08b8e933756f9a05807c7b26c63999/test/functional/JLM_Tests/src/org/openj9/test/management/TestOperatingSystemMXBean.java#L263-L264 The test obtains the values of |
I'm not at all familiar with the mxbean stuff - is there a simple way to instantiate an OperatingSystemMXBean to call those functions on it? |
I am not familiar, either. Maybe I can try writing code by looking at the testcase. |
There are debug statements in the test that print the values out so if we have an easy way to run it in debug mode that might do (if I knew where the debug stuff ends up!) |
Simple code to run:
|
Thanks :-) That shows the problem - showing 8Gb total, just under 100Gb free
The data from
Does sound like however it's doing the querying it's getting an inconsistent set of numbers - one based on the size of the container (total memory) and the other not (free memory) - two numbers which are incompatible. I'd suggest this is probably an OpenJ9/OMR bug. Should be reproducible if you run the container with |
@dinogun I think you did some work on container optimisation for OpenJ9 - would you expect the function calls above to be returning the numbers they are ain restricted container? |
Seen on the x86-64_linux jdk16+36_openj9-0.25.0-m2 build: https://ci.adoptopenjdk.net/job/Test_openjdk16_j9_extended.functional_x86-64_linux/39/consoleFull
|
Removed "AArch64:" from the title. |
@tajila fyi |
We use
This confirms @sxa analysis above. We will need to add a container aware version of |
Seen on the x86-64_linux jdk-11.0.11+5_openj9-0.26.0-m1 build.
|
@dinogun Are you able to look at this? |
Created #12420 to exclude the test on xlinux and aarch64. If there are other platforms pls let me know. |
@pshipton Seen on pLinux as well: https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_extended.functional_ppc64le_linux/117/testReport/junit/org.openj9.test.management/TestOperatingSystemMXBean/runTestOSMXBean/ |
Part of tests testOSMXBeanLocal and testOSMXBeanRemote, which run org.openj9.test.management.TestOperatingSystemMXBean.runTestOSMXBean() Issue eclipse-openj9#12038 Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
Part of tests testOSMXBeanLocal and testOSMXBeanRemote, which run org.openj9.test.management.TestOperatingSystemMXBean.runTestOSMXBean() Issue eclipse-openj9#12038 Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
The test is excluded when running on docker. Also in the 0.26.0 release branch. |
AssertionError "Free Physical Memory size cannot be greater than total Physical Memory Size." with OSMXBeanLocal tests.
Failure link
https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_extended.functional_aarch64_linux/119/ (on build-docker-fedora33-armv8-4)
https://ci.adoptopenjdk.net/view/Test_functional/job/Test_openjdk11_j9_extended.functional_aarch64_linux_xl/5/ (on build-docker-ubuntu1804-armv8-4)
https://ci.adoptopenjdk.net/view/Test_functional/job/Test_openjdk11_j9_extended.functional_aarch64_linux_xl/4/ (on build-docker-ubuntu1804-armv8-5)
https://ci.adoptopenjdk.net/view/Test_functional/job/Test_openjdk11_j9_extended.functional_aarch64_linux_xl/3/ (on build-docker-fedora33-armv8-5)
https://ci.adoptopenjdk.net/view/Test_functional/job/Test_openjdk11_j9_extended.functional_aarch64_linux_xl/1/ (on build-docker-ubuntu1804-armv8-5)
Optional info
Failure output (captured from console output)
The text was updated successfully, but these errors were encountered: