karianna
commented
3 years ago TRSS link Build URL https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/1603/ Started by user George Adams
Test_openjdk8_hs_extended.openjdk_s390x_linux hotspot_jre_1 => deep history 0/5 passed | possible issues - OK to release jdk_other_1 => deep history 0/5 passed | possible issues - OK to release jdk_security1_1 => deep history 0/4 passed | possible issues - OK to release jdk_security2_1 => deep history 0/4 passed | possible issues - OK to release jdk_security4_1 => deep history 0/4 passed | possible issues - OK to release jdk_management_1 => deep history 0/4 passed | possible issues - OK to release jdk_tools_1 => deep history 0/4 passed | possible issues - OK to release jdk_jfr_1 => deep history 0/3 passed | possible issues - OK to release jdk_instrument_1 => deep history 0/3 passed | possible issues - OK to release
Test_openjdk8_hs_extended.perf_s390x_linux renaissance-als_0 => deep history 0/5 passed | possible issues - OK to release renaissance-chi-square_0 => deep history 0/5 passed | possible issues - OK to release renaissance-dec-tree_0 => deep history 0/5 passed | possible issues - OK to release renaissance-gauss-mix_0 => deep history 0/5 passed | possible issues - OK to release renaissance-log-regression_0 => deep history 0/5 passed | possible issues - OK to release renaissance-movie-lens_0 => deep history 0/5 passed | possible issues - OK to release renaissance-par-mnemonics_0 => deep history 3/5 passed | possible issues - OK to release renaissance-philosophers_0 => deep history 0/5 passed | possible issues - OK to release
Test_openjdk8_hs_special.functional_ppc64_aix - OK to release - Host missing Dep MBCS_Tests_annotation_Ja_JP_aix_0 => deep history 2/3 passed | possible issues - OK to release MBCS_Tests_coin_ZH_CN_aix_0 => deep history 2/3 passed | possible issues - OK to release MBCS_Tests_pref_ZH_CN_aix_0 => deep history 2/3 passed | possible issues - OK to release
Test_openjdk8_hs_extended.openjdk_x86-64_mac jdk_tools_1 => deep history 0/5 passed | possible issues - OK to release jdk_jfr_1 => deep history 0/5 passed | possible issues - OK to release jdk_instrument_1 => deep history 0/5 passed | possible issues - OK to release
Test_openjdk8_hs_sanity.openjdk_ppc64_aix jdk_util_1 => deep history 1/6 passed | possible issues - OK to release
Test_openjdk8_hs_extended.openjdk_ppc64le_linux hotspot_jre_1 => deep history 0/5 passed | possible issues - OK to release jdk_other_1 => deep history 0/5 passed | possible issues - OK to release jdk_security4_1 => deep history 2/5 passed | possible issues - OK to release jdk_management_1 => deep history 0/5 passed | possible issues - OK to release jdk_tools_1 => deep history 0/5 passed | possible issues - OK to release jdk_jfr_1 => deep history 0/5 passed | possible issues - OK to release
Test_openjdk8_hs_sanity.openjdk_x86-64_windows - ⚠️ Test Job Failed ⚠️
Waiting for next available executor on ‘ci.role.test&&hw.arch.x86&&sw.os.windows’
Running on test-ibmcloud-win2012r2-x64-2 in E:\workspace\Test_openjdk8_hs_sanity.openjdk_x86-64_windows
[Pipeline] {
[Pipeline] checkout
The recommended git tool is: git
No credentials specified
> git rev-parse --is-inside-work-tree # timeout=10
ERROR: Workspace has a .git repository, but it appears to be corrupt.
hudson.plugins.git.GitException: Command "git rev-parse --is-inside-work-tree" returned status code 128:
stdout:
stderr: fatal: not a git repository (or any parent up to mount point /cygdrive)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).Followed by a failure to clean up the workspace.
Rerun - test results - OK to Release - some agent timeouts but outside of that, the rest passed.
Test_openjdk8_hs_sanity.perf_s390x_linux dacapo-h2_0 => deep history 0/11 passed | possible issues - OK to release
Test_openjdk8_hs_extended.openjdk_x86-64_windows ⚠️ Test Job Failed ⚠️
Same as the git issue on the IBM cloud machine (test-ibmcloud-win2012r2-x64-2)
rerun - This also failed due to an agent timeout Cannot contact test-azure-win2016-x64-1: java.lang.InterruptedException.
rerun 2 - Waiting on Results
Test_openjdk8_hs_extended.openjdk_x86-64_linux hotspot_jre_1 => deep history 1/5 passed | possible issues - OK to release jdk_other_1 => deep history 0/5 passed | possible issues - OK to release jdk_nio_1 => deep history 2/5 passed | possible issues - OK to release jdk_tools_1 => deep history 0/5 passed | possible issues - OK to release jdk_jfr_1 => deep history 0/5 passed | possible issues - OK to release
Test_openjdk8_hs_extended.openjdk_ppc64_aix ⚠️ Test Job Failed ⚠️
Lots of failures like
STDERR:
[2021-04-20T21:58:29.826Z] stdout: [];
[2021-04-20T21:58:29.826Z] stderr: [Unrecognized option: -client
[2021-04-20T21:58:29.826Z] Error: Could not create the Java Virtual Machine.
[2021-04-20T21:58:29.826Z] Error: A fatal exception has occurred. Program will exit.
[2021-04-20T21:58:29.826Z] ]
[2021-04-20T21:58:29.826Z] exitValue = 1
[2021-04-20T21:58:29.826Z] and crashes like:
Calculating fingerprints ... done.
[2021-04-20T22:00:03.982Z] Removing unshareable information ... done.
[2021-04-20T22:00:03.982Z] #
[2021-04-20T22:00:03.982Z] # A fatal error has been detected by the Java Runtime Environment:
[2021-04-20T22:00:03.982Z] #
[2021-04-20T22:00:03.982Z] # Internal Error (metaspaceShared_ppc.cpp:59), pid=16121890, tid=0x0000000000001415
[2021-04-20T22:00:03.982Z] # Error: Unimplemented()
[2021-04-20T22:00:03.982Z] #
[2021-04-20T22:00:03.982Z] # JRE version: (8.0_292-b10) (build )
[2021-04-20T22:00:03.982Z] # Java VM: OpenJDK 64-Bit Server VM (25.292-b10 interpreted mode aix-ppc64 compressed oops)
[2021-04-20T22:00:03.982Z] # Core dump written. Default location: /home/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_ppc64_aix/openjdk-tests/TKG/output_16189556105917/hotspot_jre_1/work/scratch/core or core.16121890
[2021-04-20T22:00:03.982Z] #
[2021-04-20T22:00:03.982Z] # An error report file with more information is saved as:
[2021-04-20T22:00:03.982Z] # /home/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_ppc64_aix/openjdk-tests/TKG/output_16189556105917/hotspot_jre_1/work/scratch/hs_err_pid16121890.log
[2021-04-20T22:00:03.982Z] #
[2021-04-20T22:00:03.982Z] # If you would like to submit a bug report, please visit:
[2021-04-20T22:00:03.982Z] # https://github.com/AdoptOpenJDK/openjdk-support/issues
[2021-04-20T22:00:03.982Z] #
[2021-04-20T22:00:03.982Z] ];
[2021-04-20T22:00:03.982Z] stderr: []
[2021-04-20T22:00:03.982Z] exitValue = 134Going to rerun the whole lot and see if it's environmental.
rerun - Failed with the same errors. - OK to release - turns out JFR is not enabled on this platform and this suite shouldn't run.
Test_openjdk8_hs_extended.perf_x86-32_windows renaissance-als_0 => deep history 0/5 passed | possible issues - OK to release renaissance-chi-square_0 => deep history 0/5 passed | possible issues - OK to release renaissance-dec-tree_0 => deep history 0/5 passed | possible issues - OK to release renaissance-gauss-mix_0 => deep history 0/5 passed | possible issues - OK to release renaissance-log-regression_0 => deep history 0/5 passed | possible issues - OK to release renaissance-movie-lens_0 => deep history 0/5 passed | possible issues - OK to release
Test_openjdk8_hs_extended.openjdk_x86-32_windows hotspot_jre_2 => deep history 0/4 passed | possible issues - OK to release jdk_other_2 => deep history 0/4 passed | possible issues - OK to release jdk_security2_2 => deep history 0/4 passed | possible issues - OK to release jdk_management_2 => deep history 0/4 passed | possible issues - OK to release jdk_jmx_2 => deep history 0/4 passed | possible issues - OK to release
gdams
smlambert
This release checklist based on the release doc captures what activities must happen during a release.
The target release date is: 20th April 2021
The release champion for this release is: Martijn Verburg
The role of the release champion is to ensure that all release activities listed in this checklist get completed (by delegation to the broader team or by the release champion themselves). The final task of the release champion during a release is to confirm that all items in the checklist were completed satisfactorily and the release can be declared complete.
Everyone participating in a release, including the release champion is requested to provide feedback into the release retrospective so that the release process can be continuously improved (through simplification and/or automation).
One Week Prior to Release:
Release Week Checklist: