-
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
fix ci: update systemd generate unit test #15796
Conversation
Two PRs have been merged causing a failure in one unit test. Fix the unit test to turn CI green again. Signed-off-by: Valentin Rothberg <[email protected]>
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.
/lgtm
/hold
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.
LGTM
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: giuseppe, Luap99, vrothberg 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 |
/hold cancel |
/hold CI is still in progress (and, sigh, flaking) |
true, but this PR is touching only a |
Can't merge until Total Success is green, though - branch protection should prevent it (at least for bots) |
@giuseppe my understanding is that CI has to be fully green before a hold can be released. Bug in the merge thingy. #10295 (comment) Anyhow, I've been trained to never, ever, ever set the merge labels until CI is green. Maybe the bug has been fixed, if so, someone please inform me. |
Now it's green. |
Two PRs have been merged causing a failure in one unit test. Fix the unit test to turn CI green again.
Signed-off-by: Valentin Rothberg [email protected]
Does this PR introduce a user-facing change?
@containers/podman-maintainers URGENT, PTAL
Just found the issue locally. I hope we can merge it quickly before it's hitting new PRs.