<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 2/13/26 9:53 PM, Nicolas Fella
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:63e39693-e71d-49de-abd2-978423662bf4@gmx.de">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">On 2/13/26 9:24 PM, Ben Cooksley
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+XidOFkmO3YXGG085sB2AofawcFeBYxdJx1Zg40wH15wRsbYg@mail.gmail.com">
<meta http-equiv="content-type"
content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Thu, Feb 12, 2026 at 1:09 PM Albert Astals
Cid <<a href="mailto:aacid@kde.org"
moz-do-not-send="true" class="moz-txt-link-freetext">aacid@kde.org</a>>
wrote:</div>
<div class="gmail_quote gmail_quote_container">
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Please
work on fixing them, otherwise i will remove the failing
CI jobs on <br>
their 4th failing week, it is very important that CI is
passing for multiple <br>
reasons.<br>
<br>
Good news: 2 repo fixed<br>
<br>
<br>
Bad news: 5 repo started failing, 1 keeps failing<br>
<br>
<br>
kontact - LAST WEEK BEFORE REMOVAL<br>
* <a
href="https://invent.kde.org/pim/kontact/-/pipelines/1162355"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://invent.kde.org/pim/kontact/-/pipelines/1162355</a><br>
* Craft Windows job running out of memory<br>
</blockquote>
<div><br>
</div>
<div>PIM folks, could we resolve this for now by dropping
KItinerary support in Craft Windows builds, or at the very
least only target a release build of KItinerary?</div>
<div>In a cache build we are running in a High Memory VM
which will have the resource to get through building this
so the fix to this is stop rebuilding the whole PIM
stack....</div>
<div><br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
kdenlive - NEW<br>
* <a
href="https://invent.kde.org/multimedia/kdenlive/-/pipelines/1162146"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://invent.kde.org/multimedia/kdenlive/-/pipelines/1162146</a><br>
* macos fails to compile<br>
<br>
<br>
kosmindoormap - NEW<br>
* <a
href="https://invent.kde.org/libraries/kosmindoormap/-/pipelines/1161455"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://invent.kde.org/libraries/kosmindoormap/-/pipelines/1161455</a><br>
* <a
href="https://invent.kde.org/libraries/kosmindoormap/-/pipelines/1161715"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://invent.kde.org/libraries/kosmindoormap/-/pipelines/1161715</a>
(stable)<br>
* Android build seems to be using the wrong binary
format? cross-compilation issue?<br>
<br>
<br>
neochat - NEW<br>
* <a
href="https://invent.kde.org/network/neochat/-/pipelines/1162323"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://invent.kde.org/network/neochat/-/pipelines/1162323</a>
(stable)<br>
* flatpak build fails<br>
</blockquote>
<div><br>
</div>
<div>Not sure why a stable branch is building against master
of libquotient, but seems like <a
href="https://invent.kde.org/network/neochat/-/commit/8ca1b8b1d387838fde1c1c448e5d2fe3a077a6e2"
moz-do-not-send="true" class="moz-txt-link-freetext">https://invent.kde.org/network/neochat/-/commit/8ca1b8b1d387838fde1c1c448e5d2fe3a077a6e2</a>
needs to be cherry picked if that is intended?</div>
<div> </div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
kgpg - NEW<br>
* <a
href="https://invent.kde.org/utilities/kgpg/-/pipelines/1161149"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://invent.kde.org/utilities/kgpg/-/pipelines/1161149</a>
<br>
* Timeout in kgpg-disable and kgpg-export<br>
<br>
<br>
kmbox - NEW<br>
* <a
href="https://invent.kde.org/pim/kmbox/-/pipelines/1162163"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://invent.kde.org/pim/kmbox/-/pipelines/1162163</a><br>
* Timeout in mbox-mboxbenchmark<br>
</blockquote>
<div><br>
</div>
<div>This test seems to be sitting on the edge of whether it
will pass or not - Qt 6.11 only just passed by running in
57 seconds vs. the timeout limit of 60 seconds.</div>
<div>What is it trying to achieve and why so many
iterations?</div>
</div>
</div>
</blockquote>
I don't follow what's going on there.<br>
<br>
<p>Locally that benchmark finishes in ~1 second here, so no
problem whatsoever.</p>
<p>On CI the first two sub-benchmarks seem completely fine, but
voidTestMD5Performance seems to hand/time out. It's not clear to
me how many iterations it does.</p>
<p>It looks like QBENCHMARK automatically adjusts the number of
iterations until the results are "good" (whatever that exactly
means). Possibly some CI conditions trigger that to go haywire.</p>
</blockquote>
<p>That said, all this seems to do is benchmark the performance of
QCryptographicHash, which is nonsensical here.</p>
<p><a class="moz-txt-link-freetext" href="https://invent.kde.org/pim/kmbox/-/merge_requests/18">https://invent.kde.org/pim/kmbox/-/merge_requests/18</a></p>
</body>
</html>