containers: Run checks for podman-remote unconditionally #19338
Merged
Conversation
This file contains 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
ricardobranco777
requested review from
pdostal,
grisu48 and
mloviska
as code owners
pdostal
approved these changes
May 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The remote tests must be run unconditionally to fail loudly if
podman-remoteis unavailable. Thewhichwas added to test SLM 6.0 but it now has podman-remote in the repos (https://bugzilla.suse.com/show_bug.cgi?id=1224050 was fixed).If we ever need this skip this again we can now set
PODMAN_BATS_SKIP_USER_REMOTE=all&PODMAN_BATS_SKIP_ROOT_REMOTE=all.Verification run: Not needed as the products we test all have podman-remote: