-
-
Notifications
You must be signed in to change notification settings - Fork 312
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
October 2024 Release Triage: JDK11 #5691
Comments
x86-64_windows ✔️ extended.openjdk
This test has failed previously (#5442 (comment)) and was successfully able to run on test-azure-win2019-x64-1 which is now marked as permanently offline in favour of win2022 machines (failure assumed to be machine specific), will consider it non-blocking. other top-level targets passing |
x86-64_linux ✔️ extended.openjdk failed as it is sending to dynamic agents and there is no make installed ?
example from https://ci.adoptium.net/job/Test_openjdk11_hs_extended.openjdk_x86-64_linux_testList_0/27/console other top-level targets passed |
x86-64_mac ✔️ extended.openjdk
|
aarch64_linux ✔️ sanity.openjdk
extended.openjdk
sanity.system
|
aarch64_mac ✔️ all top-level targets pass - https://ci.adoptium.net/job/build-scripts/job/jobs/job/release/job/jobs/job/jdk11u/job/jdk11u-release-mac-aarch64-temurin/24/ |
x86-64_alpine-linux ✔️ extended.openjdk
sanity.system
|
ppc64le_linux ✔️ extended.openjdk
sanity.system job fails on machine with config issues so rerun at https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.system_ppc64le_linux/902 - passes
|
s390x_linux ✔️ extended.openjdk |
ppc64_aix extended.openjdk
|
arm_linux sanity.openjdk
extended.openjdk
extended.perf job was terminated, rerun in https://ci.adoptium.net/job/Test_openjdk11_hs_extended.perf_arm_linux/188/ - passes
|
x86-32_windows extended.openjdk
JShellHeapDumpTest is likely non-blocking, not seen to pass on win2022 nodes (though in pass able to pass on win2019 nodes) |
https://ci.adoptium.net/job/build-scripts/job/release-openjdk11-pipeline/50/
✔️ results in these Tables means the activity has successfully completed.
⏳ results means that we are actively working on closing off the runs needed for this version, platform, binaryType.
⛔ means there is no build planned for that version/platform combination.
⏸️ means activity not yet started.
The text was updated successfully, but these errors were encountered: