-
-
Notifications
You must be signed in to change notification settings - Fork 249
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
Weekly build triage for the week starting 2023/04/15 #3330
Comments
https://ci.adoptium.net/view/Failing%20Temurin%20jobs/job/build-scripts/job/jobs/job/jdk20u/job/jdk20u-linux-arm-temurin/9/ https://ci.adoptium.net/view/Failing%20Temurin%20jobs/job/build-scripts/job/jobs/job/jdk20u/job/jdk20u-aix-ppc64-temurin/5/console https://ci.adoptium.net/view/Failing%20Temurin%20jobs/job/build-scripts/job/jobs/job/jdk17u/job/jdk17u-linux-arm-temurin/192/console https://ci.adoptium.net/view/Failing%20Temurin%20jobs/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-mac-x64-temurin/207/
https://ci.adoptium.net/view/Failing%20Temurin%20jobs/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-arm-temurin/199/ https://ci.adoptium.net/view/Failing%20Temurin%20jobs/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-aix-ppc64-temurin/221/console
All failures occurred on test-osuosl-aix715-ppc64-<1-4>. Two other tests ran on test-osuosl-aix72-ppc64-<1-2> and didn't have this problem. Machine issue? Unknown, but it looks like we were having this issue (or something that looks exactly like it) four years ago on JDK13. That problem was OS version specific, and it doesn't look like it was fixed (we just ran on an earlier OS version), so it could well be the same issue. https://ci.adoptium.net/view/Failing%20Temurin%20jobs/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-solaris-x64-temurin/307/console https://ci.adoptium.net/view/Failing%20Temurin%20jobs/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-solaris-sparcv9-temurin/295/console https://ci.adoptium.net/view/Failing%20Temurin%20jobs/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-linux-arm-temurin/266/consoleFull https://ci.adoptium.net/view/Failing%20Temurin%20jobs/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-alpine-linux-x64-temurin/245/consoleFull
https://ci.adoptium.net/view/Failing%20Temurin%20jobs/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-aix-ppc64-temurin/276/ |
3 biggest issues:
|
(Wrote this hours ago but apparently didn't clck the button to add it to the issue!) Ref the AIX ones:
That /may/ be related to adoptium/jdk@f5c8b68 based on seeing when it started failing on in jdk21 builds
https://ci.adoptium.net/view/Failing%20Temurin%20jobs/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-aix-ppc64-temurin/276 was run on an AIX 7.2 machine, so I would not expect it to run properly on AIX 7.1. https://github.com/adoptium/ci-jenkins-pipelines/pull/622/files was where that change was implemented and it's supposed to be only targetting 7.2 machines for the testing, but the error suggests that's not taking effect as it should - can you check that the test jobs and machines are labelled in a way consistent with that PR? |
@sxa - I'm confused by the second PR link listed above. From your description, I was expecting some form of code that affects the selection of test machines based on aix version. Instead, it seems to be a link to a harfbuzz version update. Please verify that that's the right PR link. Thank you. :) |
Also, analysis implies that the failed test jobs were born from a build job that was originally run before your test label change was integrated. Builds (and tests of those builds) after that point seem to run with the correct labels. |
Edited to have the correct link. |
Here's a summary of the failing builds, grouped by issue and topped with a summary. Summary
Details jdk20u-linux-arm-temurin/9 jdk20u-aix-ppc64-temurin/5 jdk11u-mac-x64-temurin/207 jdk11u-aix-ppc64-temurin/221 jdk8u-solaris-x64-temurin/307 jdk8u-alpine-linux-x64-temurin/245 |
Triage complete. No more builds this week. Release in progress. Closing. |
This week's build triage summary:
This is the week (we assume/hope) of the April-2023 Temurin release. As such, no new builds were run over the weekend.
To get a feel for the build status prior to the release, I'll be focusing on the Temurin build jobs whose last execution failed. Link.
Will include links to the failing builds below, followed by the cause of failure.
The text was updated successfully, but these errors were encountered: