-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
jdk11 jdk_compile failures on macos12 #4326
Comments
Same on test-macincloud-macos1201-x64-2 |
Two jdk_net tests failed on macos12 with different error message. https://trss.adoptium.net/deepHistory?testId=62b789e3250c3c428c3ad570 |
We would like to take those two machines offline before the issues is fixed (either update the test cases or update machine configuration?) to avoid re-triage again and again. Looks like https://ci.adoptopenjdk.net/computer/test-macincloud-macos1201-x64-1/ is offline due to some other updates. The interesting thing is both machines are labeled as macos10.10 https://ci.adoptopenjdk.net/label/macos10.10/, which is incorrect. Might be updated from macos10.10 to macos10.12? |
jdk_net with jdk18 failed https://ci.adoptopenjdk.net/job/Test_openjdk18_hs_extended.openjdk_x86-64_mac_testList_1/41/ history shows only fail on macos12 |
That looks like a separate failure from the one mentioned in the description, so perhaps it should have its own issue |
Agreed - that's an error. Updated to |
There is no JBS issue reported yet. However feels like it is the test issue. As New in macOS Big Sur 11.0.1, the system ships with a built-in dynamic linker cache of all system-provided libraries. As part of this change, copies of dynamic libraries are no longer present on the filesystem. Code that attempts to check for dynamic library presence by looking for a file at a path or enumerating a directory will fail. Instead, check for library presence by attempting to dlopen() the path, which will correctly check for the library in the cache. (62986286). Similar issue can't link object file with ld on macOS . To make those tests work with macos11+ command needs to be updated |
Does the failure show on the aarch64 builds which are on macos11.0.1? The above would suggest that it would affect those too. |
Looking at https://ci.adoptopenjdk.net/job/Test_openjdk11_hs_extended.openjdk_aarch64_mac_testList_1/17/testReport/ it looks like those tests are not run on aarch64 so the consistent option would seem to be be to exclude them on the x86-64 platform too. |
Do we have macos11? I didn't find one https://ci.adoptopenjdk.net/label/ci.role.test&&hw.arch.x86&&%28sw.os.osx%7C%7Csw.os.mac%29/ Ignore this, i didn't realize @sxa mentioned aarch64 macos11 |
@sxa those aot tests only run if VM supports AOT. Does jdk11 arch64 mac support AOT? If no tests will skip. |
Interesting - apparently not:
It says |
Yeah these seem to be IP address/socket issues. One is giving |
This keeps failing tests during the latest two releases. |
This feels like a upstream issue. Would need help to confirm from and fix in upstream. |
Same issue with github runner macos-latest(12). https://github.com/sophia-guo/runaqaTest/actions/runs/4136572808/jobs/7150623636 |
56 compiler/aot/* tests failed on test-macincloud-macos1201-x64-1 only with message:
https://ci.adoptopenjdk.net/job/Test_openjdk11_hs_extended.openjdk_x86-64_mac_testList_1/41/
https://trss.adoptium.net/deepHistory?testId=625744b172761a4c5c12015c
The text was updated successfully, but these errors were encountered: