-
-
Notifications
You must be signed in to change notification settings - Fork 301
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
jdk14u aarch64 64k builds show an error while testing on 4k machines #1864
Comments
Correction: This fix appears to claim that this issue is resolved on jdk15, so the tests shouldn't have to be fixed. It seems a more prudent use of time to simply exclude the tests (from jdk14 - aarch) while we wait for jdk14 to expire. If we see the problem on jdk15, then we can spend time on a fix. |
PR to exclude failing tests here: #1907 |
Closing this for now. If the issue returns on jdk15, we can re-open. |
This is an error I am currently having with the latest adoptopenjdk build for aarch64 PCs (https://adoptopenjdk.jfrog.io/artifactory/rpm/centos/7/aarch64/Packages/adoptopenjdk-16-hotspot-16.0.1+9-3.aarch64.rpm). How do I go about reopening and documenting this? The server in question is a free tier machine on oracle cloud, where I install this rpm manually onto a oracle linux OS. |
Please open a new issue in our adoptium-support repository |
Platform: arm64
Architecture: aarch64
The problem is that if you build jdk14u on an aarch64 machine with 64k pages, and then use it on a machine with 4k pages (and possibly the reverse too), you get this non-fatal error right before the -version output:
This was originally reported here.
However, the fix was not backported to 14, nor does the fix appear to be an actual resolution of the issue (but rather something to let the build process tolerate the error).
Since jdk14 is about to go out of service, I'm not convinced that backporting is a good use of anyone's time, however these test failures still need to be resolved for jdk14+ test runs on aarch64.
If the accepted solution for the build issue was to ignore the error message, it seems like the correct action here is to modify the tests to do the same via an OpenJDK bug.
Notes:
64k machine - build-osuosl-aix71-ppc64-2
4k machine - test-aws-ubuntu1804-armv8-1
Useful facts
The text was updated successfully, but these errors were encountered: