<div dir="ltr"><div id="gmail-:v4" class="gmail-Am gmail-aiL gmail-Al editable gmail-LW-avf gmail-tS-tW gmail-tS-tY" aria-label="Message Body" role="textbox" aria-multiline="true" style="direction:ltr;min-height:85px" tabindex="1" aria-controls=":2yl" aria-expanded="false"><div>I agree completely. I think as a group we need to be on board for always having green tests; it has been shown time and again to be one of the best ways of achieving stable, reliable software.</div><div><br></div><div>I've tried a few times to get tests running locally for the bigger projects like plasma-workspace, plasma-desktop, and kwin but they seem to have serious issues; if I remember correctly failing even though they pass on CI, as well as getting hung and not progressing. Not a locale issue, since my system is en_us.</div><div><br></div><div>If anyone has insight into how we can fix that and make them easier and more reliable to run locally it would help a lot.</div><div><br></div><div>As far as the CI goes, I think a good solution is making test passing mandatory for merging. I started our migration to this already: <a href="https://discuss.kde.org/t/test-failures-fatal-by-default-in-kde-ci/31670">https://discuss.kde.org/t/test-failures-fatal-by-default-in-kde-ci/31670</a></div><div><br></div><div>My work on that has fallen a bit by the wayside since I was hired as Plasma Software Engineer and I have been putting most of my time into KISS, but I will try to squeeze in the time to work at it..</div></div><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Jul 24, 2025 at 11:40 AM Nicolas Fella <<a href="mailto:nicolas.fella@gmx.de">nicolas.fella@gmx.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
<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><span><span>The following tests
FAILED:</span></span></div>
<div></div>
<code>
<div><span><span> 33 -
servicerunnertest (Failed)</span></span></div>
<div></div>
</code><code>
<div><span><span> 54 -
clipboardtest (Failed)</span></span></div>
<div></div>
</code><code>
<div><span><span> 55 -
devicenotifiertest (Failed)</span></span></div>
<div></div>
</code><code>
<div><span><span> 68 -
kcm_colors_test (Failed)</span></span></div>
<div></div>
</code>
<p><code><span><span> 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 href="https://invent.kde.org/sdk/selenium-webdriver-at-spi/-/issues/16" target="_blank">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>
</div>
</blockquote></div><div><br clear="all"></div><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div></div><div>Cheers,</div><div> Kristen</div></div></div>