-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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:BUILD] Packit: Adjustments for Cockpit reverse-dependency check #19753
[CI:BUILD] Packit: Adjustments for Cockpit reverse-dependency check #19753
Conversation
The cockpit team only ever supports two parallel Fedora releases, and will soon discontinue updating Fedora 37. So, instead of risking testing against an obsolete Fedora, test against the most recent stable and all development series. These are often fewer than we support, but that's totally sufficient for this purpose. [NO NEW TESTS NEEDED] - This is test configuration. Signed-off-by: Martin Pitt <[email protected]>
…it-podman These are relevant when validating upstream or selinux-policy changes, but not podman ones. This makes the revdeps tests more robust against random (non-fatal) SELinux denials or messages from other system components. [NO NEW TESTS NEEDED] - This is test configuration. Signed-off-by: Martin Pitt <[email protected]>
Awesome, someone broke c8s+epel-next-8:
Unrelated, and I can't retry tests here anyway, so I'll leave it at that. @lsm5 do you mind reviewing? Thanks! |
i've notified copr folks about it already. We can ignore those for now. |
@martinpitt will review in a bit, thanks |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lsm5, martinpitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@martinpitt did you mean you didn't have permission to run |
/cherry-pick v4.6 |
@lsm5: new pull request created: #19756 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@lsm5 ah, slash-packit may have worked, but I am not allowed to do the Re-run action in the packit status view |
@martinpitt ack. don't know if you need to be in the OWNERS file for it, or if this is a thing packit could solve on their side. I'll ask around. |
Please see the two individual commit messages for details. This will robustify the test against unrelated non-fatal unexpected message checks, seen in #19741.
Does this PR introduce a user-facing change?