-
Notifications
You must be signed in to change notification settings - Fork 33
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
Promote AdoptOpenJDK Version jdk8u272-b10 #179
Comments
TRSS link
|
I updated the comment above to remove the 38 extra entries of jdk_jfr_0 test target. Apparently Jenkins pushed the output to the console 39 times despite only 1 run of the test actually taking place (details here: adoptium/aqa-test-tools#321). |
openj9 test results (excluding failures from the newly added tests) from run https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1311/ ppc64_aix - all passed |
openj9 results from rebuild job https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1316/ x86-64_linux x86-64_linux_xl - all tests passed |
It is disconcerting that the sanity.external targets had been 'healthier' up until very recently. It appears that some 'event' occurs on Oct 14th that causes each of these to no longer run properly. I see that quarkus_quickstarts passing until Oct 14 (consistent with the last healthy hotspot run). tomee running all tcks but failing on last one, then at Oct 14 no longer executing in the same way. Did we publish a bunch of new Docker images or in some other way change the environment around that Oct 14th time frame? Do not think we would block on these external test failures, but it will be good to understand what event may cause the behaviour change. |
Agreed @smlambert |
JDK8u re-run: TRSS link Test_openjdk8_hs_sanity.external_x86-64_linux_quarkus_quickstarts Test_openjdk8_hs_sanity.external_x86-64_linux_openliberty-mp-tck Test_openjdk8_hs_sanity.external_x86-64_linux_tomee |
JDK8u re-run: TRSS link Test_openjdk8_hs_sanity.openjdk_x86-32_windows Test_openjdk8_hs_sanity.external_s390x_linux_quarkus_quickstarts Test_openjdk8_hs_sanity.openjdk_x86-64_windows Test_openjdk8_hs_sanity.perf_s390x_linux Test_openjdk8_hs_sanity.external_s390x_linux Test_openjdk8_hs_sanity.perf_x86-32_windows Test_openjdk8_hs_extended.system_x86-64_mac |
Running a Grinder on the openj9 win32 jdk/test/java/lang/ProcessBuilder/Basic.java failure just to check it was a machine issue: |
jdk8u272-b10_openj9-0.23.0: Pipelines for publishing: |
HotSpot shipped except for aarch64 - @smlambert approved the release |
Aarch64 pipeline complete: https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-linux-aarch64-hotspot/691/ TRSS link No failures |
Aarch64 HotSpot shipped - @karianna approved the release |
OpenJ9 jdk8 shipped. |
OpeJ9 macOS re-run: TRSS link NO FAILURES |
HotSpot Linux Arm32: TRSS link Test_openjdk8_hs_sanity.openjdk_arm_linux |
jdk_util failure was a timeout on CountLargeTest (which passes on rerun but is a long execution time 7+ minutes, so it will likely continue to hit timeout on occasion) jdk_jdi tests seem to be machine related, as they all pass on rerun here / running on test-sxamb-armv7l-raspbian-pi4 |
Solaris HotSpot pipeline: TRSS link NO TESTS RUN ON SOLARIS (we never have) |
@gdams To be clear to reviewers/approvers is "NO TEST FAILURES" your way of saying we haven't run any tests, or have you run some somewhere outside the pipelines? |
@sxa that is true, updating the comment |
Thanks for clarifying - I approve this going out now on the basis it's undergone the same level as testing as on previous releases (We need to change this though!) :-) |
Release build for jdk8u272-b10_openj9-0.23.0 for aarch64 “ea” started: |
jdk8u272-b10_openj9-0.23.0 for aarch64 “ea” test results, "All Green" :-) : |
I approve on the basis of that and the fact that Andrew has confirmed the metadata looks ok. Let's ship it and see if the website picks it up properly.
|
+1 to releasing jdk8u272-b10_openj9-0.23.0 for aarch64 “ea” |
Ship it! :-) |
Live and working. And since that was the last platform on JDK8u272 I'm going to close this :-) |
Java Version:
JVM:
@AdoptOpenJDK/tsc please can somebody +1 this request?
The text was updated successfully, but these errors were encountered: