Closed smlambert closed 4 years ago
OpenJ9: TRSS links: AIX and other platforms
Test_openjdk8_j9_sanity.external_x86-64_linux #266: 3 failures - these are non-blocking, they should get fixed, some are failures related to recent changes to external test targets
OpenJ9: jdk8:
checking for protoc... no
configure: error: jitserver requires protoc
configure exiting with result code 1
Hotspot JDK8u Failures:
Test_openjdk8_hs_extended.system_x86-64_mac HCRLateAttachWorkload_0 => long term failure deep history
Test_openjdk8_hs_sanity.openjdk_s390x_linux jdk_jdi_0 => long term failure deep history - test issue for further triage (did this occur in last release?) jdk_lang_0 => intermittent failure deep history jdk_util_0 => intermittent failure deep history
Test_openjdk8_hs_sanity.external_x86-64_linux_tomee tomee_test_0 => long term failure deep history Non-Blocking https://github.com/AdoptOpenJDK/TSC/issues/153#issuecomment-614390641 - (still considered non-blocking, but created test issue for triage/fixing)
Test_openjdk8_hs_sanity.system_x86-64_linux TestJlmRemoteMemoryAuth_SE80_Linux_0 => passed in grinder
Test_openjdk8_hs_sanity.external_x86-64_linux_openliberty-mp-tck openliberty_microprofile_tck_0 => long term failure deep history Non-Blocking https://github.com/AdoptOpenJDK/TSC/issues/153#issuecomment-614390641
Test_openjdk8_hs_sanity.openjdk_x86-32_windows jdk_jdi_0 => long term failure deep history
Test_openjdk8_hs_sanity.openjdk_x86-64_mac jdk_jdi_0 => long term failure deep history
Test_openjdk8_hs_sanity.external_x86-64_linux_thorntail-mp-tck thorntail_microprofile_tck_0 => long term failure deep history Non-Blocking https://github.com/AdoptOpenJDK/TSC/issues/153#issuecomment-614390641
Test_openjdk8_hs_sanity.openjdk_x86-64_windows jdk_jdi_0 => long term failure deep history
Regarding failure
pLinuxXL build failure: machine build-osuosl-centos74-ppc64le-1
checking for protoc... no configure: error: jitserver requires protoc configure exiting with result code 1
It looks like pLinux openj9 built successfully on that machine on 10th April: https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-linux-ppc64le-openj9/558/
pLinux when it worked:
checking for jitserver... yes (explicitly enabled)
checking checking that '/home/jenkins/workspace/build-scripts/jobs/jdk8u/jdk8u-linux-ppc64le-openj9/workspace/./build//freemarker-2.3.30/freemarker.jar' exists... yes
checking for sysroot...
when it failed:
checking for jitserver... yes (explicitly enabled)
checking for protoc... no
configure: error: jitserver requires protoc
Seems the check for protoc has been added?
openj9 release builds resubmitted following fix for the ppcle build issue (https://github.com/ibmruntimes/openj9-openjdk-jdk8/pull/403)
New pipeline: https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/990
TRSS link to openj9 respin pipeline: https://trss.adoptopenjdk.net/resultSummary?parentId=5e9855cd0833d14bd533b9d2
OpenJ9:
14:49:26 /home/jenkins/workspace/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/openjdk-tests/TKG/../external/external.sh --clean --tag ubuntu --version 8 --impl openj9 --dir openliberty-mp-tck; } 2>&1 | tee -a "/home/jenkins/workspace/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/openjdk-tests/TKG/../TKG/test_output_15870449669653/TestTargetResult";
14:49:26 No EXTRA_DOCKER_ARGS set
14:49:26 docker: Error response from daemon: Conflict. The container name "/openliberty-mp-tck-test" is already in use by container "81e7baff80acd9dae4af7f7c69e7443b452fbf63076800b0fd4d7415dc07437d". You have to remove (or rename) that container to be able to reuse that name.
@AdoptOpenJDK/tsc request to publish OpenJ9 jdk8u252-b09 please?
+1
+1 to publishing both openj9 and hotspot
Speaking to @gdams - we will plan to release hotspot also. Note on QA: I am working through the list of test failures and creating independent issues for each of the remaining failures so they can be properly triaged. For the release retrospective, I recommend this activity happen more regularly or at minimum the week before release so that we enter the release with a clean slate.
jdk8u252-b09 hotspot released on all platforms except for aarch64
jdk8u252-09 aarch64 https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/993/
No Test Failures! 🎉
@tsc request to publish
+1 to aarch64/HotSpot
Notarized jdk8u252-b09
build is complete: https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1001/
Test Failures:
Test_openjdk8_hs_extended.system_x86-64_mac HCRLateAttachWorkload_0 => long term failure deep history - Failed in previous release as well
Test_openjdk8_hs_sanity.system_x86-64_mac TestJlmRemoteMemoryAuth_SE80_0 => passed on re-run grinder
@tsc request to publish Notarized JDK8u build
+1
Windows and Mac openj9 releases have been rebuilt to:
Build pipeline: https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1003/ TRSS: https://trss.adoptopenjdk.net/resultSummary?parentId=5ea054e04b7a9f45690d6150 (no failures)
Windows X64 build has been downloaded from the job and checked for 'Digital Signatures' tab in Properties.
hotspot win rebuild:
https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1002/ TRSS: https://trss.adoptopenjdk.net/buildDetail?parentId=5ea011374b7a9f45690d4d29
Failures:
Test_openjdk8_hs_sanity.openjdk_x86-64_windows jdk_util_0 => passed in grinder jdk_jdi_0 => long term failure deep history
Test_openjdk8_hs_sanity.openjdk_x86-32_windows jdk_jdi_0 => long term failure deep history
@tsc - request to publish the openj9 release rebuilds as jdk8u252-b09.1_openj9-0.20.0.
@lumpfish +1 (note that @tsc
is a user not @AdoptOpenJDK/tsc
I noticed I was doing the same thing earlier
You mean I should use tag @AdoptOpenJDK/tsc to alert tsc members?
correct 👍
@AdoptOpenJDK/tsc request to publish hotspot win rebuild
Approved - go for it
openj9 rebuilds published: https://github.com/AdoptOpenJDK/openjdk8-binaries/releases/tag/jdk8u252-b09.1_openj9-0.20.0
Java Version: jdk8u252-b09
JVM:
@AdoptOpenJDK/tsc please can somebody +1 this request?