Remove beakerlib tests #1256
Merged
Remove beakerlib tests #1256
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
We are not running these anywhere and we don't want to have tests that require internal RH configuration upstream anyway.
|
Cockpit tests failed for commit b33e854. @martinpitt, @jelly, @mvollmer please check. |
|
Something major just broke in rawhide a few hours ago, which completely breaks cockpit, in all projects (not just c-podman). We are investigating. For urgent stuff, please ignore rawhide-cockpit-revdeps run and just look at f39. |
|
OK, that selinux-policy rawhide update broke cockpit hard, but the emergency update fixed it. Please retry the rawhide-revdeps test here and also in PR #1255, they should go green again. |
tbzatek
approved these changes
Feb 8, 2024
vojtechtrefny
merged commit c885f45
into
storaged-project:master
12 of 18 checks passed
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.
We are not running these anywhere and we don't want to have tests that require internal RH configuration upstream anyway.