test: Skip currently failing opensuse-tumbleweed/other tests#22903
Merged
martinpitt merged 1 commit intocockpit-project:mainfrom Feb 19, 2026
Merged
test: Skip currently failing opensuse-tumbleweed/other tests#22903martinpitt merged 1 commit intocockpit-project:mainfrom
martinpitt merged 1 commit intocockpit-project:mainfrom
Conversation
This establishes a baseline for introducing opensuse-tumbleweed into our CI. We'll start with the `/ohter` scenario. There are currently 111 passing and 47 failing tests. A few of them are obvious, like crypto-policies and setroubleshoot not being available on Tumbleweed, adjust their skips accordingly. For the rest, just mass-skip them with "TODO: fix for OpenSUSE", which is easy enough to grep. After that, we can enable them step by step with actual fixes. E.g. large swaths of functionality is broken due to PackageKit.
martinpitt
added
the
no-test
allisonkarlitskaya
approved these changes
Feb 19, 2026
Member
allisonkarlitskaya
left a comment
allisonkarlitskaya
left a comment
There was a problem hiding this comment.
'ohter' in commit message, but this can go in, thanks :)
martinpitt
added a commit
to martinpitt/bots
that referenced
this pull request
Feb 19, 2026
cockpit-project/cockpit#22903 skipped enough tests so that the remaining ones can finally become gates. A similar thing still needs to happen for the other three scenarios, step by step!
martinpitt
added a commit
to cockpit-project/bots
that referenced
this pull request
Feb 19, 2026
cockpit-project/cockpit#22903 skipped enough tests so that the remaining ones can finally become gates. A similar thing still needs to happen for the other three scenarios, step by step!
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This establishes a baseline for introducing opensuse-tumbleweed into our CI. We'll start with the
/ohterscenario. There are currently 111 passing and 47 failing tests. A few of them are obvious, like crypto-policies and setroubleshoot not being available on Tumbleweed, adjust their skips accordingly. For the rest, just mass-skip them with "TODO: fix for OpenSUSE", which is easy enough to grep.After that, we can enable them step by step with actual fixes. E.g. large swaths of functionality is broken due to PackageKit.
FYI @Lunarequest @Nykseli
This run was the first ever that we ran on our CI in years, triggered in #22901. Let's land this first to avoid regressions in the future, then enable this, and make the other pending PRs green!