-
-
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
October 2024 Release Triage: JDK17 #5689
Comments
x86-64_mac ✔️ waiting on extended.openjdk (https://ci.adoptium.net/job/Test_openjdk17_hs_extended.openjdk_x86-64_mac/181/)
rerun at: https://ci.adoptium.net/job/Test_openjdk17_hs_extended.openjdk_x86-64_mac_testList_2/24 - passes other top-level targets passing |
waiting on extended.openjdk (https://ci.adoptium.net/job/Test_openjdk17_hs_extended.openjdk_x86-64_windows/183/) As we have marked win2019 machines offline and they were previously the only nodes where the bean tests were passing, we see the following failures in the rerun
These are known issues (#5616), that were excluded in master via #5617 but not cherrypicked to release branch. Consider non-blocking. other top-level targets passing |
aarch64_linux ✔️ extended.openjdk
sanity.system
extended.system
|
aarch64_mac ✔️ BUILD FAILURE, no tests run
Rebuild at https://ci.adoptium.net/job/build-scripts/job/release-openjdk17-pipeline/71/ Release Summary Report for release-openjdk17-pipelineReport generated at: Wed, 16 Oct 2024 19:43:42 GMT TRSS Build and TRSS Grid View jdk17u-release-mac-aarch64-temurin Test_openjdk17_hs_extended.openjdk_aarch64_mac Test_openjdk17_hs_extended.openjdk_aarch64_mac_rerun ✅ SUCCESS ✅ java -version
Test_openjdk17_hs_extended.openjdk_aarch64_mac_testList_1 extended.openjdk
|
s390x_linux ✔️ extended.openjdk
rerun passes
|
ppc64_aix extended.openjdk
Sophia - seems as July release #5443 (comment) extended.perf |
arm_linux sanity.openjdk
extended.openjdk
extended.perf run appears to have been terminated, relaunch at https://ci.adoptium.net/job/Test_openjdk17_hs_extended.perf_arm_linux/193 - passes
Sophia - sun/security/util/Debug/DebugOptions.java JBS https://bugs.openjdk.org/browse/JDK-8339713 - consider non-blocker. |
riscv64_linux ✔️ sanity.functional extended.functional
sanity.openjdk
extended.openjdk
extended.perf
|
ppc64le_linux ✔️
This means no test jobs were launched. Rerun smoke tests here: https://ci.adoptium.net/job/build-scripts/job/jobs/job/release/job/jobs/job/jdk17u/job/jdk17u-release-linux-ppc64le-temurin_SmokeTests/24 - passes Run the 9 top-level test targets here: https://ci.adoptium.net/view/Test_grinder/job/AQA_Test_Pipeline/379/
Compilation fails, InetAddress.ofLiteral cannot find symbol, known issue and won't be fixed upstream until Jan 2025 release, so needed exclusion in release branch (https://bugs.openjdk.org/browse/JDK-8299813). Consider non-blocking.
|
x86-32_windows ✔️ extended.openjdk - non-blocking, known failures
These are 'known' failures (most are HeadlessException) that should likely get excluded as we will not be running with a desktop session open under automation.
JShellHeapDumpTest has an issue where it needs a particular configuration on the machine or fails with pipe closed
|
@jiekang could you please add https://bugs.openjdk.org/browse/JDK-8339713 Affects Version/s with 17? Thanks. |
@sophia-guo Done. I would like to add a comment along the lines of: We saw this failing for JDK 17 arm32 as well here: <link-to-GitHub-issue>. But to a bug-specific issue rather than this release one. Can a separate issue be made to track this failure? |
@jiekang as there is a JBS I'd like not to add a duplicate one here as this will require extra work to track it especially no extra helpful information is provided. |
https://ci.adoptium.net/job/build-scripts/job/release-openjdk17-pipeline/70/
✔️ 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: