Promote AdoptOpenJDK Version jdk8u272-b10

[gdams]

Java Version:

JVM:

• [ ] OpenJ9
• [x] Hotspot

@AdoptOpenJDK/tsc please can somebody +1 this request?

[gdams]

TRSS link Build URL https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1309/ Started by user George Adams

⚠️ jdk8u-linux-s390x-hotspot has a build result of ABORTED ⚠️

Test_openjdk8_hs_sanity.openjdk_ppc64_aix jdk_lang_0 => deep history 10/11 passed - non-blocking java.lang.OutOfMemoryError - passes on rerun

Test_openjdk8_hs_sanity.external_s390x_linux - quarkus_quickstarts test fail, consistent with openj9 below, start failing around Oct 14th (seems like an environment change)

Test_openjdk8_hs_sanity.openjdk_x86-64_windows jdk_jdi_0 => deep history 0/11 passed - config issue JDWP exit error JVMTI_ERROR_INVALID_LOCATION(24): One or more of the library paths supplied to jdwp, likely by sun.boot.library.path, is too long. [linker_md.c:60]

Test_openjdk8_hs_sanity.openjdk_x86-32_windows jdk_jdi_0 => deep history 2/12 passed - same config issue as x64win above, passes on 2 ibm machines (test-ibmcloud-win2012r2-x64-1 & test-ibmcloud-win2012r2-x64-2) should look at the path on those machines to see differences

Test_openjdk8_hs_sanity.perf_s390x_linux dacapo-h2_0 => deep history 0/13 passed - issue raised https://github.com/AdoptOpenJDK/openjdk-tests/issues/2028, will be non-blocking but would be good to see if last release jdk can be run without issue

Test_openjdk8_hs_extended.system_x86-64_mac HCRLateAttachWorkload_0 => deep history 2/13 passed - well-known infra issue, https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/1274

Test_openjdk8_hs_sanity.system_s390x_linux LambdaLoadTest_Hotspot_0 => deep history 7/13 passed - intermittently fails with OOM error, needs issue raised

[smlambert]

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: https://github.com/AdoptOpenJDK/openjdk-test-tools/issues/321).

[smlambert]

I've also moved all of the newly added tests failure reports to this comment (and out of the summary above which now only contains reports of the tests that we have used for previous releases).

Test_openjdk8_hs_extended.openjdk_x86-64_windows hotspot_jre_0 => deep history 0/1 passed jdk_awt_0 => deep history 0/1 passed jdk_other_0 => deep history 0/1 passed jdk_security1_0 => deep history 0/1 passed jdk_security2_0 => deep history 0/1 passed jdk_security3_0 => deep history 0/1 passed jdk_management_0 => deep history 0/1 passed jdk_jmx_0 => deep history 0/1 passed

Test_openjdk8_hs_special.functional_ppc64_aix MBCS_Tests_annotation_Ja_JP_aix_0 => deep history 0/1 passed

Test_openjdk8_hs_extended.openjdk_x86-32_windows hotspot_jre_0 => deep history 0/1 passed jdk_awt_0 => deep history 0/1 passed jdk_other_0 => deep history 0/1 passed jdk_security1_0 => deep history 0/1 passed jdk_security2_0 => deep history 0/1 passed jdk_security3_0 => deep history 0/1 passed jdk_management_0 => deep history 0/1 passed jdk_jmx_0 => deep history 0/1 passed

Test_openjdk8_hs_extended.perf_s390x_linux renaissance-als_0 => deep history 0/1 passed renaissance-chi-square_0 => deep history 0/1 passed renaissance-db-shootout_0 => deep history 0/1 passed renaissance-dec-tree_0 => deep history 0/1 passed renaissance-gauss-mix_0 => deep history 0/1 passed renaissance-log-regression_0 => deep history 0/1 passed renaissance-movie-lens_0 => deep history 0/1 passed renaissance-par-mnemonics_0 => deep history 0/1 passed renaissance-philosophers_0 => deep history 0/1 passed

Test_openjdk8_hs_extended.openjdk_s390x_linux

Test_openjdk8_hs_extended.openjdk_ppc64le_linux hotspot_jre_0 => deep history 0/1 passed jdk_awt_0 => deep history 0/1 passed jdk_other_0 => deep history 0/1 passed jdk_security1_0 => deep history 0/1 passed jdk_security3_0 => deep history 0/1 passed jdk_security4_0 => deep history 0/1 passed jdk_management_0 => deep history 0/1 passed jdk_tools_0 => deep history 0/1 passed jdk_jfr_0 => deep history 0/1 passed jdk_2d_0 => deep history 0/1 passed Post Test => deep history 0/1 passed

Test_openjdk8_hs_extended.perf_x86-32_windows renaissance-als_0 => deep history 0/1 passed renaissance-chi-square_0 => deep history 0/1 passed renaissance-db-shootout_0 => deep history 0/1 passed renaissance-dec-tree_0 => deep history 0/1 passed renaissance-gauss-mix_0 => deep history 0/1 passed renaissance-log-regression_0 => deep history 0/1 passed renaissance-movie-lens_0 => deep history 0/1 passed

Test_openjdk8_hs_extended.external_s390x_linux kafka_test_0 => deep history 0/1 passed example-test_0 => deep history 0/1 passed WycheproofTests_0 => deep history 0/1 passed quarkus_java_test_0 => deep history 0/1 passed lucene_solr_nightly_smoketest_0 => deep history 0/1 passed tomcat_test_0 => deep history 0/1 passed wildfly_test_0 => deep history 0/1 passed camel_test_0 => deep history 0/1 passed jenkins_test_0 => deep history 0/1 passed scala_test_0 => deep history 0/1 passed

Test_openjdk8_hs_extended.openjdk_x86-64_mac hotspot_jre_0 => deep history 0/1 passed jdk_other_0 => deep history 0/1 passed jdk_security1_0 => deep history 0/1 passed jdk_security3_0 => deep history 0/1 passed jdk_management_0 => deep history 0/1 passed jdk_tools_0 => deep history 0/1 passed jdk_jfr_0 => deep history 0/1 passed jdk_instrument_0 => deep history 0/1 passed jdk_imageio_0 => deep history 0/1 passed jdk_2d_0 => deep history 0/1 passed

Test_openjdk8_hs_extended.openjdk_ppc64_aix hotspot_jre_0 => deep history 0/1 passed jdk_awt_0 => deep history 0/1 passed jdk_other_0 => deep history 0/1 passed jdk_security1_0 => deep history 0/1 passed jdk_security3_0 => deep history 0/1 passed jdk_security4_0 => deep history 0/1 passed jdk_tools_0 => deep history 0/1 passed jdk_jfr_0 => deep history 0/39 passed

Test_openjdk8_hs_extended.external_ppc64le_linux WycheproofTests_0 => deep history 0/1 passed lucene_solr_nightly_smoketest_0 => deep history 0/1 passed quarkus_java_test_0 => deep history 0/1 passed tomcat_test_0 => deep history 0/1 passed wildfly_test_0 => deep history 0/1 passed example-test_0 => deep history 0/1 passed scala_test_0 => deep history 0/1 passed jenkins_test_0 => deep history 0/1 passed kafka_test_0 => deep history 0/1 passed camel_test_0 => deep history 0/1 passed

Test_openjdk8_hs_extended.perf_ppc64_aix Post Test => deep history 0/1 passed

[lumpfish]

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 ppc64le_linux - all passed ppc64le_linux_xl - all passed s390x_linux - all passed s390x_linux_xl - all passed x86-32_windows - one failure, raised https://github.com/eclipse/openj9/issues/10975 x86-64_linux - Not all test jobs were submitted, resubmitted via https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1316/ x86-64_linux_xl - Not all test jobs were submitted, resubmitted via https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1316/ x86-64_mac - all passed x86-64_mac_xl - all passed x86-64_windows - all passed x86-64_windows_xl - all passed

[lumpfish]

openj9 results from rebuild job https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1316/

x86-64_linux Three failures from sanity.external quarkus_quickstarts_test_0: https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.external_x86-64_linux_quarkus_quickstarts/109/ openliberty_microprofile_tck_jdk8_j9: https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/432/ tomee_test_j9_0: https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.external_x86-64_linux_tomee/390/ All other tests passed

x86-64_linux_xl - all tests passed

[smlambert]

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.

[sxa]

Agreed @smlambert Doesn't look like the failure is on a new machine although it took me a while to find the last one that ran on the same machine: Passing run: https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.external_x86-64_linux_quarkus_quickstarts/101/consoleFull Failing run: https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.external_x86-64_linux_quarkus_quickstarts/109/consoleFull Both on https://ci.adoptopenjdk.net/computer/test-packet-ubuntu1604-x64-3/ I'm not aware of any changes that have been put on those systems recently.

[smlambert]

There has not been any suspect PRs in openjdk-tests repo from that timeframe.

There seems to be a lot of activity in openjdk-docker repo from 9-10 days ago, though I am not sure if they are suspects or not:

We run external tests by pulling the AdoptOpenJDK images tagged 'nightly' and mapping the nightly or upstream JDK to run the test suites that get set up in the container.

[gdams]

JDK8u re-run:

TRSS link Build URL https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1317/ Started by user George Adams

Test_openjdk8_hs_sanity.external_x86-64_linux_quarkus_quickstarts quarkus_quickstarts_test_0 => deep history 1/2 passed

Test_openjdk8_hs_sanity.external_x86-64_linux_openliberty-mp-tck openliberty_microprofile_tck_jdk8_hs_0 => deep history 0/2 passed

Test_openjdk8_hs_sanity.external_x86-64_linux_tomee tomee_test_hs_0 => deep history 1/2 passed

Test_openjdk8_hs_sanity.external_x86-64_linux

[gdams]

JDK8u re-run:

TRSS link Build URL https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1315/ Started by user George Adams

Test_openjdk8_hs_sanity.openjdk_x86-32_windows jdk_jdi_0 => deep history 2/10 passed

Test_openjdk8_hs_sanity.external_s390x_linux_quarkus_quickstarts quarkus_quickstarts_test_0 => deep history 2/8 passed

Test_openjdk8_hs_sanity.openjdk_x86-64_windows jdk_jdi_0 => deep history 0/9 passed

Test_openjdk8_hs_sanity.perf_s390x_linux dacapo-h2_0 => deep history 0/9 passed

Test_openjdk8_hs_sanity.external_s390x_linux

Test_openjdk8_hs_sanity.perf_x86-32_windows

Test_openjdk8_hs_extended.system_x86-64_mac HCRLateAttachWorkload_0 => deep history 2/9 passed

Test_openjdk8_hs_sanity.system_x86-32_windows

[andrew-m-leonard]

Running a Grinder on the openj9 win32 jdk/test/java/lang/ProcessBuilder/Basic.java failure just to check it was a machine issue: https://ci.adoptopenjdk.net/job/Grinder/4287/ Green

[andrew-m-leonard]

jdk8u272-b10_openj9-0.23.0: Pipelines for publishing:

• https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1311/

[gdams]

HotSpot shipped except for aarch64 - @smlambert approved the release

[gdams]

Aarch64 pipeline complete: https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-linux-aarch64-hotspot/691/

TRSS link Build URL https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1318/ Started by user George Adams

No failures

[gdams]

Aarch64 HotSpot shipped - @karianna approved the release

[andrew-m-leonard]

OpenJ9 jdk8 shipped.

[gdams]

OpeJ9 macOS re-run:

TRSS link Build URL https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1321/ Started by user George Adams

NO FAILURES

[gdams]

HotSpot Linux Arm32:

TRSS link Build URL https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1326/ Started by user George Adams

Test_openjdk8_hs_sanity.openjdk_arm_linux jdk_util_0 => deep history 1/7 passed jdk_jdi_0 => deep history 5/7 passed

[smlambert]

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

[gdams]

Solaris HotSpot pipeline:

TRSS link Build URL https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1330/ Started by user George Adams

NO TESTS RUN ON SOLARIS (we never have)

[sxa]

@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?

[gdams]

@sxa that is true, updating the comment

[sxa]

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!) :-)

[andrew-m-leonard]

Release build for jdk8u272-b10_openj9-0.23.0 for aarch64 “ea” started: https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1333/

[andrew-m-leonard]

jdk8u272-b10_openj9-0.23.0 for aarch64 “ea” test results, "All Green" :-) : https://trss.adoptopenjdk.net/resultSummary?parentId=5f9aaae57702786daf8c1e91

[sxa]

jdk8u272-b10_openj9-0.23.0 for aarch64 “ea” test results, "All Green" :-) : https://trss.adoptopenjdk.net/resultSummary?parentId=5f9aaae57702786daf8c1e91

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.

12:17:22      "version": {
12:17:22          "minor": 0,
12:17:22          "security": 272,
12:17:22          "pre": "ea",
12:17:22          "adopt_build_number": null,
12:17:22          "major": 8,
12:17:22          "version": "1.8.0_272-ea-b10",
12:17:22          "semver": "8.0.272-ea+10",
12:17:22          "build": 10,
12:17:22          "opt": null
12:17:22      },

[smlambert]

+1 to releasing jdk8u272-b10_openj9-0.23.0 for aarch64 “ea”

[karianna]

Ship it! :-)

[sxa]

Live and working. And since that was the last platform on JDK8u272 I'm going to close this :-)