-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
aarch64 mac jdk11/18 : jdk_nio consistently failed on test-macstadium-macos11-arm64-2 #2682
Comments
@sophia-guo I guess that since we have a machine it passes on this is not critical for the release? |
Added link above, and here Rerun Failed target in Grinder on same machine |
@sxa not critical. Just a note might hit the same issue for other release version. |
Agreed. Although I think it's best that we take that penalty for this cycle and re-run as Grinders if required given the limited number of systems we have just now. |
Referenced machine is no longer present in the CI and has been replaced with orka machines - re-running on those:
Noting that it's not clear from this issue what the original failure was. |
Also noting that https://ci.adoptium.net/job/Test_openjdk11_hs_extended.openjdk_aarch64_mac/ seems to be passing jdk_nio consistently. |
Some more tests:
|
Upstream issue showing a similar error with other tests: https://bugs.openjdk.org/browse/JDK-8144003 Based on that issue, here are other affected tests:
Grinder with all three tests:
Numbers in brackets are from |
Noting that due to other problems - most recently adoptium/temurin-build#4058 - we haven't had a jdk11u/mac/aarch64 build for a while and so there is a lack of reliable recent history of this execution (I couldn't easily track down anything in TRSS for it) |
Based on
All of them have |
aarch64 mac jdk11 : jdk_nio consistently failed on test-macstadium-macos11-arm64-2
Test_
job on Test_openjdk11_hs_extended.openjdk_aarch64_mac_testList_0Any other details:
https://trss.adoptium.net/deepHistory?testId=62d7d4f9250c3c428ca02918
adoptium/aqa-tests#3868 (comment)
The text was updated successfully, but these errors were encountered: