-
Notifications
You must be signed in to change notification settings - Fork 142
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
ci: Remove priority from Testing farm repositories #1307
ci: Remove priority from Testing farm repositories #1307
Conversation
Testing farm sets priority of their repositories to 9 which means the repo is prioritized over all other repositories including our Copr repo with daily builds preventing the latest libblockdev from being installed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
deprioritize!
Cockpit tests failed for commit 8d62013. @martinpitt, @jelly, @mvollmer please check. |
That rawhide failure may be a flake, but looking at the logs I just noticed that both f40 and rawhide install the wrong cockpit version:
That's the distro version, not the one from our main COPR builds. That's outright wrong.. I'll look into that today. It's not a regression due to this priority change though, it happened in e.g. #1306 too |
@@ -10,6 +10,9 @@ prepare: | |||
script: | |||
- sudo dnf install -y 'dnf-command(copr)' | |||
- sudo dnf copr enable -y @storage/udisks-daily | |||
# TF prioritizes Fedora tag repo over all others, in particular our daily COPR | |||
- for f in $(grep -l -r 'testing-farm-tag-repository' /etc/yum.repos.d); do sed -i '/priority/d' "$f" ;done | |||
- sudo dnf -y update |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you worried/did you observe that the test setup installed packages from the t-f repository which are newer than your COPR? We have often seen this in Cockpit, e.g. when there is a mass rebuild in rawhide and all the revisions are suddenly -2 instead of -1. Then you need distro-sync
here, not update
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when there is a mass rebuild in rawhide and all the revisions are suddenly -2 instead of -1
We have a workaround for this -- our packit daily builds have release -99
to make sure we are always newer even with all the rebuilds.
Sorry, I read the log wrong. The initially installed version is indeed from the distro/tag repository, but later on we also do this priority hacking: main_builds_repo="$(ls /etc/yum.repos.d/*cockpit*main-builds* 2>/dev/null || true)"
if [ -n "$main_builds_repo" ]; then
echo 'priority=0' >> "$main_builds_repo"
dnf distro-sync -y 'cockpit*'
fi and that installed the correct versions. So that Either way, please ignore here -- it's obviously unrelated to the priority change (however, you may still want to move to |
We started to see this in cockpit PRs as well (e.g. cockpit-project/cockpit#20892), so it's a recent rawhide regression. We'll deal with that on our side. |
FTR: This "regression" appeared because Fedora 41 branched off and rawhide == f42 now. It's actually a very old bug in Fedora already. We adjusted our naughty tracker, and that test will be green on retry/next run. Sorry for the noise. |
This hack is actually copied from cockpit -- cockpit-project/cockpit#19547 :-) I spent half day trying to figure out why our newer version of libblockdev is not installed even after checking that the Copr repo is enabled and explicitly calling |
54111b5
into
storaged-project:master
Testing farm sets priority of their repositories to 9 which means the repo is prioritized over all other repositories including our Copr repo with daily builds preventing the latest libblockdev from being installed.