<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi,</p>
<p>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.</p>
<p>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.</p>
<div class="js-log-line job-log-line"><span
class="job-log-line-content"><span class="">The following tests
FAILED:</span></span></div>
<div class="js-log-line job-log-line"></div>
<code data-testid="job-log-content" class="job-log gl-block">
<div class="js-log-line job-log-line"><span
class="job-log-line-content"><span class=""> 33 -
servicerunnertest (Failed)</span></span></div>
<div class="js-log-line job-log-line"></div>
</code><code data-testid="job-log-content" class="job-log gl-block">
<div class="js-log-line job-log-line"><span
class="job-log-line-content"><span class=""> 54 -
clipboardtest (Failed)</span></span></div>
<div class="js-log-line job-log-line"></div>
</code><code data-testid="job-log-content" class="job-log gl-block">
<div class="js-log-line job-log-line"><span
class="job-log-line-content"><span class=""> 55 -
devicenotifiertest (Failed)</span></span></div>
<div class="js-log-line job-log-line"></div>
</code><code data-testid="job-log-content" class="job-log gl-block">
<div class="js-log-line job-log-line"><span
class="job-log-line-content"><span class=""> 68 -
kcm_colors_test (Failed)</span></span></div>
<div class="js-log-line job-log-line"></div>
</code>
<p><code data-testid="job-log-content" class="job-log gl-block"><span
class="job-log-line-content"><span class=""> 69 -
kcm_cursortheme_test (Failed)</span></span></code></p>
<p>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.</p>
<p>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.</p>
<p>Furthermore, when I try to investigate failures locally I find
myself unable to even run then relevant appium tests locally
(<a class="moz-txt-link-freetext" href="https://invent.kde.org/sdk/selenium-webdriver-at-spi/-/issues/16">https://invent.kde.org/sdk/selenium-webdriver-at-spi/-/issues/16</a>),
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.</p>
<p>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.</p>
<p>Cheers</p>
<p>Nico<br>
</p>
<p></p>
</body>
</html>