Skip to content
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

Closed
1 of 2 tasks
gdams opened this issue Oct 22, 2020 · 29 comments
Closed
1 of 2 tasks

Promote AdoptOpenJDK Version jdk8u272-b10 #179

gdams opened this issue Oct 22, 2020 · 29 comments

Comments

@gdams
Copy link
Member

gdams commented Oct 22, 2020

Java Version:

JVM:

  • OpenJ9
  • Hotspot

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

@gdams
Copy link
Member Author

gdams commented Oct 22, 2020

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 adoptium/aqa-tests#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, adoptium/infrastructure#1274

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

@karianna karianna added this to TODO in openjdk-tsc via automation Oct 22, 2020
@karianna karianna added this to the October 2020 milestone Oct 22, 2020
@karianna karianna moved this from TODO to In Progress in openjdk-tsc Oct 22, 2020
@smlambert
Copy 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).

@smlambert
Copy link

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
Copy link

lumpfish commented Oct 23, 2020

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 eclipse-openj9/openj9#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
Copy link

@smlambert
Copy link

smlambert commented Oct 23, 2020

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
Copy link
Member

sxa commented Oct 23, 2020

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
Copy link

smlambert commented Oct 23, 2020

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:
Screen Shot 2020-10-23 at 10 04 13 AM

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.

@andrew-m-leonard
Copy link

andrew-m-leonard commented Oct 23, 2020

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
Copy link

jdk8u272-b10_openj9-0.23.0: Pipelines for publishing:

@gdams
Copy link
Member Author

gdams commented Oct 23, 2020

HotSpot shipped except for aarch64 - @smlambert approved the release

@gdams
Copy link
Member Author

gdams commented Oct 23, 2020

@gdams
Copy link
Member Author

gdams commented Oct 23, 2020

Aarch64 HotSpot shipped - @karianna approved the release

@andrew-m-leonard
Copy link

OpenJ9 jdk8 shipped.

@gdams
Copy link
Member Author

gdams commented Oct 24, 2020

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
Copy link
Member Author

gdams commented Oct 27, 2020

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
Copy link

smlambert commented Oct 27, 2020

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
Copy link
Member Author

gdams commented Oct 28, 2020

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
Copy link
Member

sxa commented Oct 28, 2020

@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
Copy link
Member Author

gdams commented Oct 28, 2020

@sxa that is true, updating the comment

@sxa
Copy link
Member

sxa commented Oct 28, 2020

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
Copy link

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
Copy link

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

@sxa
Copy link
Member

sxa commented Oct 29, 2020

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
Copy link

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

@karianna
Copy link
Member

Ship it! :-)

@sxa
Copy link
Member

sxa commented Oct 30, 2020

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

@sxa sxa closed this as completed Oct 30, 2020
openjdk-tsc automation moved this from In Progress to Done Oct 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
openjdk-tsc
  
Done
Development

No branches or pull requests

6 participants