<div dir="ltr"><div dir="ltr">On Sat, Feb 14, 2026 at 4:42 AM Sune Vuorela <<a href="mailto:nospam@vuorela.dk">nospam@vuorela.dk</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">On 2026-02-13, Harald Sitter <<a href="mailto:sitter@kde.org" target="_blank">sitter@kde.org</a>> wrote:<br>
> On Fri, Feb 13, 2026 at 12:37 PM Ben Cooksley <<a href="mailto:bcooksley@kde.org" target="_blank">bcooksley@kde.org</a>> wrote:<br>
>> Resource utilisation wise, i've not looked into whether there has been a significant bump in the number of jobs, but over the past year some additional CD support has been added so that indicates some trouble there.<br>
><br>
> Going off on a tangent: if the resources aren't sufficient for the<br>
> development of our flagship products (ruqola is not one, nor is<br>
> messagelib, but also I don't know what either do without looking them<br>
> up so maybe they are crucial to something 🤷♂️) then we need to put<br>
> more resources up.<br>
<br>
ruqola is a chat client for rocket.chat whatever that is. It seems that<br>
a linux build takes 10 minutes so I'm a bit surprised that it shows up.<br></blockquote><div><br></div><div>As of the time of writing, Ruqola sits at just shy of 92 CI hours for the month. Those were spent on:</div><div><br></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)"> name | time_used | job_count </span><br>---------------------------+-----------------+-----------
<br> freebsd150_qt610 | 15:48:25.723164 | 36
<br> windows_qt610 | 14:34:28.443605 | 36
<br> craft_macos_qt6_arm64 | 10:52:15.859244 | 16
<br> craft_macos_qt6_x86_64 | 10:06:29.462264 | 15
<br> craft_windows_qt6_x86_64 | 08:23:30.426858 | 19
<br> suse_tumbleweed_qt611 | 06:53:40.993381 | 36
<br> suse_tumbleweed_qt610 | 06:18:00.728263 | 36
<br> flatpak-amd64 | 06:01:36.990186 | 19
<br> alpine_qt610 | 05:07:18.644338 | 36
<br> craft_appimage_qt6_x86_64 | 03:58:42.797741 | 19
<br> build_clazy | 01:51:31.541318 | 6
<br> pre-commit | 01:24:42.861058 | 36
<br> cppcheck | 00:19:15.611089 | 36
<br> json-validation | 00:07:53.72674 | 36<br>
<br></span></div><div>Ruqola has 9 tests that timeout on FreeBSD, with a one minute long timeout that means across 36 builds, approximately 5 and half hours of CI time (roughly one third of all FreeBSD time) </div><div>That's 5.9% of all CI time spent on Ruqola (and realistically the 21 hours spent on MacOS should be removed as that is different hardware - if we do that it's 7.6%) essentially wasted on 9 broken tests.</div><div><br></div><div>Windows builds take 20 minutes to complete, which will in part be due to the sheer number of files that make up Ruqola. </div><div>NTFS performs poorly with large numbers of files, which will in turn be hurting Ruqola build times.</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>
Messagelib is quite in the heart of our email offerings. A linux build<br>
seems to take 4-5 minutes, so I'm also a bit surprised that that shows<br>
up here.<br></blockquote><div><br></div><div>See my reply to Volker for the stats on that.</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>
But yeah. it looks like we should acquire some extra builders.<br>
<br>
/Sune<br>
<br></blockquote><div><br></div><div>Cheers,</div><div>Ben </div></div></div>