-
Notifications
You must be signed in to change notification settings - Fork 49
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
p-s ignored a PR for F34 on a non-main branch #975
Comments
Is this related to #973? |
there was no info in logs about creating any copr projects - actually the logs are way too sparse |
This is happening also for |
Another weird behavior is that my configuration for f34-devel branch is not applied correctly. When you look on the configuration it should be started for Rawhide, 34 and ELN but it's started for Rawhide and ELN only. It seems to me that it's getting configuration from master branch instead of You can see that on this PR: rhinstaller/anaconda#3173 |
Hm, I was working on this not so long ago, but then it seems the fix was not a complete one. I'll check once more. |
I now tried to enable packit for all releases in cockpit-podman. F32/33/rawhide now actually work (except for issue #987), but F34 is forever stuck in "packit/testing-farm-fedora-34-x86_64 Pending — RPM build is in progress... ". The link points to https://prod.packit.dev/copr-build/83879 , which finished some 25 minutes ago already. I also don't see a single F34 test on https://dashboard.packit.dev/jobs → Tests, which seems to suggest that F34 tests are generally ignored/broken right now? Some missing config in packit infra perhaps? Not sure if that is the same root cause as this bug. If not, I'm happy to open a new issue for this. |
There was F34 compose missing in Testing farm, but that (#979) should be fixed now. EDIT: And the not updated checks for |
So just to make sure what's required output of this issue:
|
@jkonecny12 I've checked |
Everything seems to be working correctly a newer PR rhinstaller/anaconda#3221. I may have been a problem of rebase in that case sorry for the noise. |
@jkonecny12 no worries, rebasing is hard :) @mfocko thank you for such a thorough investigation! is there anything else which needs to be done here or shall we close this one? |
@jkonecny12 better to check than have a bug :D @TomasTomecek I'll check the statuses for rhinstaller/anaconda#3165, cause I'd expect at least SRPM build, otherwise we're done here |
use case: Anaconda team is setting up a maintenance branch for F34 where they configure packit to build and test only for F34. Packit did not set any status for this PR: https://github.com/rhinstaller/anaconda/pull/3165/files
Logs for a
/packit build
comment:The matching copr project does not exist: https://copr.fedorainfracloud.org/coprs/packit/rhinstaller-anaconda-3165/
Why did packit ignored this event?
The text was updated successfully, but these errors were encountered: