-
Notifications
You must be signed in to change notification settings - Fork 33
Promote AdoptOpenJDK Version jdk-11.0.9+11 #182
Comments
openj9 triage:
aarch64 sanity.openjdk: |
TRSS link
|
JDk11 re-run on failing platforms + linux (x64/aarch64) https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk11-pipeline/1229/ |
OpenJ9 Release Pipelines: |
OpenJ9 Test results:
|
OpenJ9 shipped. |
AIX rebuild: TRSS link Test_openjdk11_hs_extended.system_ppc64_aix |
Hotspot looks fine, all failures except one are known non-blockers. The only unknown/untriaged failure of the hotspot set is: Test_openjdk11_hs_sanity.openjdk_x86-32_windows Appears to be a relatively recent test case addition into the openjdk group, see notes in adoptium/aqa-tests#2029 (comment) failing for at least 75 days with: java.lang.UnsatisfiedLinkError: 'long CheckHandles.getProcessHandleCount()' Do not know if it has ever passed on win32 platform. Grinder: https://ci.adoptopenjdk.net/job/Grinder/4305/ |
@smlambert thanks for the update, I'll proceed with shipping 11 |
JDK11 hotspot shipped |
OpeJ9 macOS re-run: TRSS link NO FAILURES |
Shenandoah missing from HotSpot JDK11, Fixed in adoptium/temurin-build#2177. Checked WIn/x32 and it accepts the option:
Summary:
|
@AdoptOpenJDK/tsc Request to ship the above Shenandoah rebuild of JDK11/HotSpot please? Summary of test issues in previous comment TL;DR: WIndows perf hang, rerun ok. macos rogue core file on machine, re-run elsewhere still in progress. |
Versions with Shenandoah now available as 11.0.9+11.1. Everything now complete with this release, so closing. Retrospective for the releases are in #181 |
Java Version:
JVM:
@AdoptOpenJDK/tsc please can somebody +1 this request?
The text was updated successfully, but these errors were encountered: