CI tests in Plasma

[Nicolas Fella]

Hi,

for the last few weeks the CI pipelines in plasma-workspace and 
plasma-desktop have been broken, and we have become accustomed to 
ignoring them. Needless to say that's bad, and it needs to change.

In plasma-workspace for most of the time it was only clipboardtest 
that's failing, but since recently it looks like more of them are failing.

The following tests FAILED:
|
33 - servicerunnertest (Failed)
||
54 - clipboardtest (Failed)
||
55 - devicenotifiertest (Failed)
||
68 - kcm_colors_test (Failed)
|

|69 - kcm_cursortheme_test (Failed)|

Why clipboardtest started failing in the first place isn't clear to me. 
Some of the other tests could be explained by recent CI changes.

In plasma-desktop kcm_kded_test and kcm_keys_test. Both are failing 
because of newly introduced warnings from Kirigami code, and despite the 
problem being openly visible and me pointing out the problem in chat no 
fix was made.

Furthermore, when I try to investigate failures locally I find myself 
unable to even run then relevant appium tests locally 
(https://invent.kde.org/sdk/selenium-webdriver-at-spi/-/issues/16), and 
for a long time I remember having trouble with tests being broken when 
running locally due to e.g. being sensitive to non-english locale.

Note that I don't want to blame any particular person(s) here. This 
appears to be partly a social problem in that we collectively got so 
used to flaky tests that we started ignoring broken pipelines. That's 
not a healthy situation to be in though.

Cheers

Nico
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20250724/9711352d/attachment.htm>