Re: KDE Gear projects with failing CI (master + stable) (23 June 2026)

Ben Cooksley <[email protected]> Thu, 2 Jul 2026 23:11:23 +1200
Newsgroups gmane.comp.kde.devel.general
Message-ID <CA+XidOGPxxEuncfSDVre7LCmswM5ofsuP07n-q2i_RD2Coa_5A@mail.gmail.com>
--000000000000d14ae106559edfa9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 1, 2026 at 4:55=E2=80=AFAM Volker Krause <[email protected]> wrot=
e:

> On Tuesday, 30 June 2026 12:00:05 Central European Summer Time Ben
> Cooksley
> wrote:
> > On Sat, Jun 27, 2026 at 8:17=E2=80=AFPM Volker Krause <[email protected]>=
 wrote:
> > > On Donnerstag, 25. Juni 2026 12:00:31 Mitteleurop=C3=A4ische Sommerze=
it Ben
> > >
> > > Cooksley wrote:
> > > > > kalarm - 2nd week
> > > > >
> > > > >  * https://invent.kde.org/pim/kalarm/-/pipelines/1271931
> > > > >
> > > > >   * craft windows job timed out
> > > > >
> > > > > kontact - 2nd week
> > > > >
> > > > >  * https://invent.kde.org/pim/kontact/-/pipelines/1273055
> > > > >  * https://invent.kde.org/pim/kontact/-/pipelines/1271145 (stable=
)
> > > > >
> > > > >   * craft windows job ran out of memory
> > > >
> > > > Given the Craft jobs for both Kontact and KAlarm both rely on
> building
> > >
> > > the
> > >
> > > > entire PIM stack from scratch (due to the master requirement) i'm n=
ot
> > >
> > > sure
> > >
> > > > if keeping these builds is sustainable.
> > > > Building all the PIM stack pieces takes the CI nodes the better par=
t
> of
> > >
> > > 40
> > >
> > > > minutes or so (including signing) and we don't yet have a solution =
to
> > >
> > > avoid
> > >
> > > > that as far as i'm aware.
> > > >
> > > > Can anyone from PIM comment as to whether other options are possibl=
e?
> > >
> > > Kontact is heavy, in the same league as other large applications
> > > struggling
> > > with the 1h limit. The obvious optimizations (no tests, unity builds,
> etc)
> > > seem already be exhausted.
> >
> > *nod*. Something that will need to be worked through - aside from Konta=
ct
> > the only other application i'm aware of hitting this limit lately is
> > Kdenlive?
> >
> > > Moving more libraries to Frameworks helps a tiny bit, but that is a
> very
> > > slow
> > > process.  We have just done that with KMime, the full impact on Craft
> > > isn't
> > > there yet though, needs at least
> > >
> https://invent.kde.org/packaging/craft-blueprints-kde/-/merge_requests/15=
7
> > > 7
> > > still.
> > >
> > > This wont really help with the most heavy parts though, things like
> > > messagelib
> > > are essentially KMail.
> >
> > Makes sense.
> >
> > This particular build is failing due to Itinerary I believe which has
> some
> > rather large CPP files that MSVC needs a significant amount of memory t=
o
> > build.
> > Don't suppose it would be easy to break those up into smaller, less
> > problematic pieces?
> >
> > The build VMs have 16GB RAM so they're reasonably well equipped.
>
> There is one particularly large file (
> https://invent.kde.org/pim/kitinerary/-/
> blob/master/src/lib/knowledgedb/trainstationdb_data.cpp
> <https://invent.kde.org/pim/kitinerary/-/blob/master/src/lib/knowledgedb/=
trainstationdb_data.cpp>),
> which I would like
> to see split up as well, but that's not entirely straightforward.
>
> However, it looks like it's not choking on that one, but rather
> consistently
> on https://invent.kde.org/pim/kitinerary/-/blob/master/src/lib/era/
> fcbticket3.h (or any of it's similar siblings). That isn't particularly
> large
> (1k lines), but contains some compile-time computation magic behind the
> harmless looking macros. Breaking this up is not entirely impossible
> either,
> but it would be rather inconvenient as those files are more or less a 1:1
> translation of official specifications and match their structure.
>
> Instead I would (again) suggest to disable the itinerary plugin for KMail
> on
> Windows, which is the only reason this is built. As Itinerary itself isn'=
t
> available for Windows and as the KDE Connect integration in the plugin is
> not
> compatible with KDE Connect on Windows, two thirds of its functionality
> are
> not available there anyway.
>
> Ie. revert https://invent.kde.org/packaging/craft-blueprints-kde/-/commit=
/
> 4507061e1323a346598382b226e3f562c6638eb3
> <https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/4507061e1=
323a346598382b226e3f562c6638eb3>
> .
>

Seems like a reasonable solution to disable it.
That should be done by
https://invent.kde.org/packaging/craft-blueprints-kde/-/merge_requests/1584


>
> Best regards,
> Volker


Cheers,
Ben

--000000000000d14ae106559edfa9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><span style=3D"background-color:transpare=
nt">On Wed, Jul 1, 2026 at 4:55=E2=80=AFAM Volker Krause &lt;<a href=3D"mai=
lto:[email protected]">[email protected]</a>&gt; wrote:</span></div><div class=
=3D"gmail_quote gmail_quote_container"><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex">On Tuesday, 30 June 2026 12:00:05 Central European Summer Tim=
e Ben Cooksley <br>
wrote:<br>
&gt; On Sat, Jun 27, 2026 at 8:17=E2=80=AFPM Volker Krause &lt;<a href=3D"m=
ailto:[email protected]" target=3D"_blank">[email protected]</a>&gt; wrote:<br>
&gt; &gt; On Donnerstag, 25. Juni 2026 12:00:31 Mitteleurop=C3=A4ische Somm=
erzeit Ben<br>
&gt; &gt; <br>
&gt; &gt; Cooksley wrote:<br>
&gt; &gt; &gt; &gt; kalarm - 2nd week<br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt;=C2=A0 * <a href=3D"https://invent.kde.org/pim/kalarm/-/=
pipelines/1271931" rel=3D"noreferrer" target=3D"_blank">https://invent.kde.=
org/pim/kalarm/-/pipelines/1271931</a><br>
&gt; &gt; &gt; &gt;=C2=A0 <br>
&gt; &gt; &gt; &gt;=C2=A0 =C2=A0* craft windows job timed out<br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; kontact - 2nd week<br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt;=C2=A0 * <a href=3D"https://invent.kde.org/pim/kontact/-=
/pipelines/1273055" rel=3D"noreferrer" target=3D"_blank">https://invent.kde=
.org/pim/kontact/-/pipelines/1273055</a><br>
&gt; &gt; &gt; &gt;=C2=A0 * <a href=3D"https://invent.kde.org/pim/kontact/-=
/pipelines/1271145" rel=3D"noreferrer" target=3D"_blank">https://invent.kde=
.org/pim/kontact/-/pipelines/1271145</a> (stable)<br>
&gt; &gt; &gt; &gt;=C2=A0 <br>
&gt; &gt; &gt; &gt;=C2=A0 =C2=A0* craft windows job ran out of memory<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Given the Craft jobs for both Kontact and KAlarm both rely o=
n building<br>
&gt; &gt; <br>
&gt; &gt; the<br>
&gt; &gt; <br>
&gt; &gt; &gt; entire PIM stack from scratch (due to the master requirement=
) i&#39;m not<br>
&gt; &gt; <br>
&gt; &gt; sure<br>
&gt; &gt; <br>
&gt; &gt; &gt; if keeping these builds is sustainable.<br>
&gt; &gt; &gt; Building all the PIM stack pieces takes the CI nodes the bet=
ter part of<br>
&gt; &gt; <br>
&gt; &gt; 40<br>
&gt; &gt; <br>
&gt; &gt; &gt; minutes or so (including signing) and we don&#39;t yet have =
a solution to<br>
&gt; &gt; <br>
&gt; &gt; avoid<br>
&gt; &gt; <br>
&gt; &gt; &gt; that as far as i&#39;m aware.<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Can anyone from PIM comment as to whether other options are =
possible?<br>
&gt; &gt; <br>
&gt; &gt; Kontact is heavy, in the same league as other large applications<=
br>
&gt; &gt; struggling<br>
&gt; &gt; with the 1h limit. The obvious optimizations (no tests, unity bui=
lds, etc)<br>
&gt; &gt; seem already be exhausted.<br>
&gt; <br>
&gt; *nod*. Something that will need to be worked through - aside from Kont=
act<br>
&gt; the only other application i&#39;m aware of hitting this limit lately =
is<br>
&gt; Kdenlive?<br>
&gt; <br>
&gt; &gt; Moving more libraries to Frameworks helps a tiny bit, but that is=
 a very<br>
&gt; &gt; slow<br>
&gt; &gt; process.=C2=A0 We have just done that with KMime, the full impact=
 on Craft<br>
&gt; &gt; isn&#39;t<br>
&gt; &gt; there yet though, needs at least<br>
&gt; &gt; <a href=3D"https://invent.kde.org/packaging/craft-blueprints-kde/=
-/merge_requests/157" rel=3D"noreferrer" target=3D"_blank">https://invent.k=
de.org/packaging/craft-blueprints-kde/-/merge_requests/157</a><br>
&gt; &gt; 7<br>
&gt; &gt; still.<br>
&gt; &gt; <br>
&gt; &gt; This wont really help with the most heavy parts though, things li=
ke<br>
&gt; &gt; messagelib<br>
&gt; &gt; are essentially KMail.<br>
&gt; <br>
&gt; Makes sense.<br>
&gt; <br>
&gt; This particular build is failing due to Itinerary I believe which has =
some<br>
&gt; rather large CPP files that MSVC needs a significant amount of memory =
to<br>
&gt; build.<br>
&gt; Don&#39;t suppose it would be easy to break those up into smaller, les=
s<br>
&gt; problematic pieces?<br>
&gt; <br>
&gt; The build VMs have 16GB RAM so they&#39;re reasonably well equipped.<b=
r>
<br>
There is one particularly large file (<a href=3D"https://invent.kde.org/pim=
/kitinerary/-/blob/master/src/lib/knowledgedb/trainstationdb_data.cpp" rel=
=3D"noreferrer" target=3D"_blank">https://invent.kde.org/pim/kitinerary/-/<=
br>
blob/master/src/lib/knowledgedb/trainstationdb_data.cpp</a>), which I would=
 like <br>
to see split up as well, but that&#39;s not entirely straightforward.<br>
<br>
However, it looks like it&#39;s not choking on that one, but rather consist=
ently <br>
on <a href=3D"https://invent.kde.org/pim/kitinerary/-/blob/master/src/lib/e=
ra/" rel=3D"noreferrer" target=3D"_blank">https://invent.kde.org/pim/kitine=
rary/-/blob/master/src/lib/era/</a><br>
fcbticket3.h (or any of it&#39;s similar siblings). That isn&#39;t particul=
arly large <br>
(1k lines), but contains some compile-time computation magic behind the <br=
>
harmless looking macros. Breaking this up is not entirely impossible either=
, <br>
but it would be rather inconvenient as those files are more or less a 1:1 <=
br>
translation of official specifications and match their structure.<br>
<br>
Instead I would (again) suggest to disable the itinerary plugin for KMail o=
n <br>
Windows, which is the only reason this is built. As Itinerary itself isn&#3=
9;t <br>
available for Windows and as the KDE Connect integration in the plugin is n=
ot <br>
compatible with KDE Connect on Windows, two thirds of its functionality are=
 <br>
not available there anyway.<br>
<br>
Ie. revert <a href=3D"https://invent.kde.org/packaging/craft-blueprints-kde=
/-/commit/4507061e1323a346598382b226e3f562c6638eb3" rel=3D"noreferrer" targ=
et=3D"_blank">https://invent.kde.org/packaging/craft-blueprints-kde/-/commi=
t/<br>
4507061e1323a346598382b226e3f562c6638eb3</a>.<br></blockquote><div><br></di=
v><div>Seems like a reasonable solution to disable it.</div><div>That shoul=
d be done by <a href=3D"https://invent.kde.org/packaging/craft-blueprints-k=
de/-/merge_requests/1584">https://invent.kde.org/packaging/craft-blueprints=
-kde/-/merge_requests/1584</a></div><div>=C2=A0</div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">
<br>
Best regards,<br>
Volker</blockquote><div><br></div><div>Cheers,</div><div>Ben=C2=A0</div></d=
iv></div>

--000000000000d14ae106559edfa9--