July 2024 JDK11 Dry-run Triage #5435
Comments
|
aarch64_mac ✔️ |
|
x86-64_mac ✔️ sanity.openjdk has 1 failing testcase in original, passes in rerun on test-macstadium-macos1014-x64-1.adoptopenjdk.net |
|
x86-64_linux ✔️ sanity.openjdk, jdk11_tier1_pack200 fails has 1 testcase failing tools/pack200/Pack200Props.java in original and in rerun (though rerun is failing because it can not find the testcase class, likely a test framework issue), will need to rerun the entire target for now, jdk11_tier1_pack200 Testcase times out in original (on test-docker-ubi9-x64-1) run rerun jdk11_tier1_pack200 in Grinder/10891 passes extended.openjdk has 3 failing testcases in original, all pass in rerun |
|
x86-64_windows ⏳ extended.openjdk 2 testcases fail in original (testwin2022dc and bld-win2022-1), 1 fails in rerun on test-azure-win2022-x64-3 JShellHeapDumpTest.java fails with: |
|
aarch64_linux ✔️ sanity.system 2 targets fail in original, 1 fails in rerun rerun TestJlmRemoteMemoryAuth_1 in Grinder/10592 passes extended.openjdk 4 testcases fail in original on test-docker-fedora39-armv8l-1, pass in rerun test-docker-ubuntu2004-armv8l-2 |
|
x86-64_alpine-linux Only 1 testcase failure in original, fails on rerun as not supported, needs exclusion |
|
ppc64le_linux ✔️ extended.openjdk has 1 testcase failure in original, passes in rerun |
|
s390x_linux ⏳ sanity.system 1 target TestJlmRemoteMemoryNoAuth_1 fails in original and rerun extended.system has 3 targets fail in original, pass in rerun extended.perf has 1 target fail in original and rerun extended.openjdk has 7 targets fail in original, 2 pass in rerun |
|
ppc64_aix ✔️ extended.openjdk has 3 testcases fail in the original, 2 fail in rerun (on test-osuosl-aix72-ppc64-6) Rerun in Grinder/10589 and Grinder/10590 - both Grinders fail, can retry on TCJenkins, but should consider Temurin specific exclusion, TCGrinder/4362 passes |
|
arm_linux BUILD FAILURE (no tests run, JDK binary fails to build on dockerhost-equinix-ubuntu2004-armv8-1 |
|
x86-32_windows |
x86-64_windowshttps://trss.adoptium.net/allTestsInfo?buildId=66928860d24e1b006e2059ce&limit=5&hasChildren=true jdk_jdi_0 build-azure-win2022-x64-2 Likely same WSL issue as for jdk 21 #5437 (comment) jdk_tools_0 test-azure-win2022-x64-1 Likely same debug issue as for jdk 17 #5436 (comment) jdk_tools_1 test-azure-win2022-x64-1 Same as jdk_tools_0 |
|
Closing as we head into actual release triage. |
github-project-automation
bot
moved this from In Progress
to Done
in 2024 3Q Adoptium Plan
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TBD
https://ci.adoptium.net/job/build-scripts/job/release-openjdk11-pipeline/47/
✔️ 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: