-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
Jan 2024 CPU - Temurin JDK8 release triage #4984
Comments
x86-32_windows build failure, needs relaunching |
jdk8_aarch64Linux_AQAvitTaps.zip waiting for sanity.openjdk and extended.openjdk test results
Sophia: extended: testlist1 - rerun of failed testcases in Grinder/8588 - 36/40 testcases passed testlis2 - rerun testList_2 - rerun failed targets testList TESTLIST=jdk_time_0,jdk_time_1,jdk_jmx_1,jdk_tools_0 tck temurin https://ci.eclipse.org/temurin-compliance/view/Grinder/job/Grinder/4001/ - passed |
x86-64_windows jdk8_x64Windows_AQAvitTaps.zip all top-level targets pass |
x86-64_mac
Test_openjdk8_hs_extended.openjdk_x86-64_mac_testList_0 failed with Connection broken - rerun here with increased TIME_LIMIT as it hit the default 10 hr limit passes
|
x86-64_linux - build job has queued for 21+ hrs waiting for a build node ‘build&&linux&&x64&&dockerBuild’
Sophia: versioncheck issue #4243, not excluded, might be intermittent. SL/Jan19 - thanks for the note @sophia-guo - that is the final failure seen here, we will consider it non-blocking and look at that #4243 issue in upcoming iteration |
arm_linux - jdk8 triggered separately waiting for tag and pipeline trigger Release Summary Report for release-openjdk8-pipelineReport generated at: Mon, 22 Jan 2024 17:26:43 GMT TRSS Build and TRSS Grid View sanity.functional - pass sanity.perf - machine fail test-sxa-armv7l-ubuntu2004-odroid-1 Connection broken, rerun in https://ci.adoptium.net/job/Test_openjdk8_hs_sanity.perf_arm_linux/461 - passes extended.perf - machine fail test-sxa-armv7l-ubuntu2004-odroid-1 Connection broken, rerun in https://ci.adoptium.net/job/Test_openjdk8_hs_extended.perf_arm_linux/129/ - passes extended.functional - rerun https://ci.adoptium.net/job/Test_openjdk8_hs_extended.functional_arm_linux/448 (machine failure on first try, test-sxa-armv7l-ubuntu2004-odroid-1 Connection broken) - passes sanity.openjdk
java/util/stream/*OpTest cases fail in this way
extended.openjdk - machine fail, test-sxa-armv7l-ubuntu2004-odroid-1 Connection broken, rerun at https://ci.adoptium.net/job/Test_openjdk8_hs_extended.openjdk_arm_linux/121/
These 2 hotspot_jre testcases are testing G1 GC, which is disabled on arm_linux JDK8, so these testcases should be excluded for this platform/version.
I have marked test-sxa-armv7l-ubuntu2004-odroid-1 offline in order to try and get through the remainder of testing. |
x86-64_alpine-linux - build queued on ‘dockerhost-equinix-ubuntu2204-x64-1’ sanity.system - TestJlmLocal_0 failed in original run, passed in automatic rerun extended.openjdk failed targets:
TODO: confirm whether we have any x86-64_alpine-linux where the 2 jdk_net IPv6 test cases can run and pass, for now consider non-blocking
|
x86-32_windows - initial build failed respin build: Release Summary Report for release-openjdk8-pipelineReport generated at: Thu, 18 Jan 2024 00:17:35 GMT TRSS Build and TRSS Grid View sanity.openjdk -> jdk_jdi_jdk8 failed in original run, passed in automatic rerun all other test targets passed |
ppc64_aix
|
Release Summary Report for release-openjdk8-pipeline
Report generated at: Wed, 17 Jan 2024 05:39:04 GMT
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptium.net/job/build-scripts/job/release-openjdk8-pipeline/37/
Started by upstream project "build-scripts/utils/releaseTrigger_jdk8u" build number 1848 at 1/16/2024, 10:03:10 PM
✔️ results in these Tables means the activity has successfully completed.
⏳ results means that we are actively working on closing off the runs needed for this version, platform, binaryType.
⛔ means there is no build planned for that version/platform combination.
⏸️ means activity not yet started.
The text was updated successfully, but these errors were encountered: