-
-
Notifications
You must be signed in to change notification settings - Fork 316
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
January 2025 Dry-run Triage - JDK21 #5850
Comments
aarch64_alpine-linux sanity.openjdk UNSTABLE, Rerun job has 5 failing testcases, rerun in Grinder/12268 - jdk/jshell/ExternalEditorTest.java should be excluded (same issue on x64 alpine-linux), serviceability tests pass on rerun
extended.openjdk UNSTABLE, rerun job has 6 testcases failing, rerun in Grinder/12269
|
x86-64_alpine-linux sanity.openjdk UNSTABLE, with 1 testcase failure
Likely related to this upstream change openjdk/jdk17u-dev@05b2ff4 (as indicated by https://bugs.openjdk.org/browse/JDK-8308554), in any event, we are building headless alpine-linux, so an ExternalEditorTest failure is non-blocking, will look to exclude. Also noting https://bugs.openjdk.org/browse/JDK-8285987 (executing shell scripts without Upstream code is missing * @ requires !vm.musl
|
aarch64_linux sanity.openjdk rerun passes on test-aws-rhel76-armv8-1
extended.openjdk rerun passes on test-docker-fedora41-armv8-1
|
aarch64_mac extended.openjdk rerun passes
|
ppc64 AIX sanity.openjdk rerun has 1 testcase failing
|
ppc64le_linux sanity.openjdk rerun passed on test-docker-ubuntu2204-ppc64le-2
extended.openjdk rerun passes on test-docker-ubuntu2204-ppc64le-3
|
riscv64_linux sanity.openjdk rerun has 1 testcase failure serviceability/sa/TestJhsdbJstackMixed.java, rerun in Grinder/12332 - passes Grinder_20250116233558_riscvJDK21.tap.txt
extended.openjdk rerun passes
extended.perf rerun passes
sanity.system rerun passes
|
s390x_linux sanity.openjdk rerun passes
extended.openjdk rerun passes
|
x86-64_linux extended.openjdk rerun passes
|
x86-64_mac sanity.openjdk status FAILURE, rerun passes
original failure was
extended.openjdk - 1 child job status FAILURE passes on rerun, 1 child job has status UNSTABLE, rerun isn't working due to a bug in our hotspot_custom code has 1 testcase failure, runtime/CommandLine/OptionsValidation/TestOptionsWithRanges.java#id7 Test results: no tests selected, so need to rerun the entire target to check if its reproducible, rerun hotspot_runtime in Grinder/12301 passes when not run on test-macstadium-macos1014-x64-1 (where it crashed)
Original failure was a crash running on test-macstadium-macos1014-x64-1 (hotspot_runtime target in https://ci.adoptium.net/job/Test_openjdk21_hs_extended.openjdk_x86-64_mac_testList_3/18/), error log: hs_err_pid83924.log
|
aarch64_windows extended.functional job FAILURE and can not rerun as it fails on test-azure-win11-aarch64-1 before hitting the rerun logic in the test pipeline, manual rerun required (rebuild here https://ci.adoptium.net/job/Test_openjdk21_hs_extended.functional_aarch64_windows/109/) passes Test_openjdk21_hs_extended.functional_aarch64_windows.tap.txt
sanity.openjdk job UNSTABLE, rerun has 4 testcase failures on test-azure-win11-aarch64-1 java/lang/Thread/virtual/stress/Skynet.java#default.Skynet_default times out MachCodeFramesInErrorFile
ReadFromNoaccessArea
RedefineSharedClassJFR
extended.openjdk job FAILURE, rerun also fails (in same way that extended.functional fails above), manual rerun here https://ci.adoptium.net/job/Test_openjdk21_hs_extended.openjdk_aarch64_windows_rerun/30/
Failed testcases in manual rerun:
|
Close in favour of real release triage activities. |
Pipelines 41 (all platforms) and 42 (rerun of alpine-linux platforms)
✔️ 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.
check java/beans exclusions are cherrypicked to v1.0.5-releasefixed in #5863The text was updated successfully, but these errors were encountered: