-
-
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
July 2024 JDK8 Release Triage #5441
Comments
x86-64_mac ✔️ sanity.openjdk 1 testcase failure in original and rerun
extended.openjdk 4 targets fail in original, 1 target with 1 testcase failure in rerun, rerun in Grinder/10627 passes
|
x86-64_linux extended.openjdk 2 testcase failures, 1 still fails in rerun, rerun in Grinder/10626
|
x86-64_windows all pass |
aarch64_linux extended.openjdk 2 targets fail, pass on rerun
|
x86-64_alpine-linux extended.openjdk, 2 testcases fail, 1 fails in rerun
TestTLS12.java
|
ppc64le_linux ✔️ exttended.openjdk, 7 testcases fail in original and pass in rerun
|
ppc64_aix ✔️ extended.openjdk, 2 testcases fail in original, pass in rerun
|
sparcv9_solaris All test jobs hitting this issue (same as seen in dry run)
Try rerunning all test jobs in AQA_Test_Pipeline/337 Rerun again in AQA_Test_Pipeline/340/ extended.openjdk has 1 testcase failure, TestCompilerCompile which times out (NoSuchMethodError warnings seem suspicious, need to look at the test code, wondering if this is not a valid test to run against sparcv9 solaris, given its jfr, will consider it non-blocking
sanity.system failed, rerun at https://ci.adoptium.net/job/Test_openjdk8_hs_sanity.system_sparcv9_solaris/419 passes extended.system failed, rerun at https://ci.adoptium.net/job/Test_openjdk8_hs_extended.system_sparcv9_solaris/412 passes FYI @steelhead31 |
x86-64_solaris sanity.openjdk was aborted, so rerun in https://ci.adoptium.net/job/Test_openjdk8_hs_sanity.openjdk_x86-64_solaris_testList_0/7/ passes extended.openjdk failed, so rerun in https://ci.adoptium.net/job/Test_openjdk8_hs_extended.openjdk_x86-64_solaris_testList_0/12
extended.openjdk Original run failed with:
all other top-level test targets passing |
x86-32_windows extended.openjdk, 3 targets fail in original, 1 target with 1 testcase failing in rerun
compiler/loopopts/TestUnrollLimitPreciseType.java#test1 using unrecognized VM option, test not applicable for win32, consider non-blocking
|
I'll take a look at this, need to find a root cause for this... |
Thanks! Yes, I have not seen this happen anytime previous to this July dry-run and release pipelines |
Afte
I've fixed the issues with Xvfb, but believe this to have been caused by the Xvfb session being started, then the following script causing the test shell to drop out, leaving some rogue xframe related to files. I've tidied up the rogue files, and fixed the permissions to reduce all of the errors with starting Xvfb, and only the known warning "Unable to edit egid" remaining, which can be ignored. The root cause of the failures thou appear to be related to this script, which does not execute cleanly on Solaris/Sparc
|
arm_linux Release Summary Report for release-openjdk8-pipelineReport generated at: Tue, 23 Jul 2024 18:41:08 GMT TRSS Build and TRSS Grid View extended.perf - dacapo_xalan and renaissance-finagle-http core dump in original run, on rerun on test-docker-ubuntu2004-armv7l-4 renaissance-finagle-http passes and dacapo_xalan fails with (rerun in Grinder/10653) passes
sanity.system 1 target TestJlmRemoteNotifierProxyAuth_2 fails in original and passes in rerun extended.openjdk - 4 targets failing in original, hotspot_jre rerun in Grinder/10651
jdk_net_2,jdk_jfr_2,jdk_security3_2 is now running in Grinder/10655 passes with the exception of the TestUnrollLimitPreciseType.java testcase which should be excluded TestUnrollLimitPreciseType should be excluded on this platform
sanity.openjdk has 15 testcase failures in original, 9 failing in rerun, run 9 in TCGrinder/4441
|
x86-64_mac Failures: extended.openjdk: |
all tapfiles except upstream arm32 https://ci.adoptium.net/view/Test_grinder/job/TAP_Collection/11/ |
I had thought arm is using the different repo, which has to be collected separately. However it's wrong. As long as it is triggered by same upstream build pipeline we can collect all by once. Here is the build https://ci.adoptium.net/view/Test_grinder/job/TAP_Collection/19/ |
Release Summary Report for release-openjdk8-pipeline
Warning: The release summary report is not yet complete. Currently, it only contains partial results.
Report generated at: Thu, 18 Jul 2024 14:21:12 GMT
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptium.net/job/build-scripts/job/release-openjdk8-pipeline/65/
Started by upstream project "build-scripts/utils/releaseTrigger_jdk8u" build number 2618 at 7/18/2024, 9:29:35 AM
✔️ 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.
java.security.ProviderException: sun.security.pkcs11.wrapper.PKCS11Exception: CKR_ATTRIBUTE_VALUE_INVALID
#5420 known, non-blocking failure, NSS lib relatedjava.security.ProviderException: sun.security.pkcs11.wrapper.PKCS11Exception: CKR_ATTRIBUTE_VALUE_INVALID
#5420 known, non-blocking failure, NSS lib relatedSeparate pipeline and branch
The text was updated successfully, but these errors were encountered: