Conversation
Child buildArch subtask triggered from Koji scratch build for a noarch package can be run on any architecture - noarch, x86_64, aarch64, etc. This means that retriggers can pick a different arch than the job before, which breaks the CI reporting - two different Log Detective analysis jobs are created, when the more recent one should have replaced the old one. Assisted-by: Codex gpt-5.6-terra Signed-off-by: Jan Matufka <jmatufka@redhat.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Child buildArch subtask triggered from Koji scratch build for a noarch package can be run on any architecture - noarch, x86_64, aarch64, etc. This means that retriggers can pick a different arch than the job before, which breaks the CI reporting - two different Log Detective analysis jobs are created, when the more recent one should have replaced the old one.
Noarch package LD analyses will be named
target-noarch(i.e.f45-noarch), regardless of whether the build happened on x86_64, aarch64, or whatever. This should fix the CI reporting issue. We rely on the fact that for noarch packages, buildArch tasks havelabel=="noarch".I checked around 600 different buildArch koji tasks from last 2 months, none had
arch == 'noarch'and at the same timelabel != 'noarch', so this fix should be safe.RELEASE NOTES BEGIN
Fix LD analysis overwriting for noarch packages built on different arches.
RELEASE NOTES END