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

--nextPart7FnrksZtQwyIUzv_qTJLsQ
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Volker Krause <[email protected]>
To: [email protected]
Subject:  Re: KDE Gear projects with failing CI (master + stable) (23 June 2026)
Date: Tue, 30 Jun 2026 18:54:22 +0200
Message-ID: <[email protected]>
Organization: KDE
In-Reply-To:  <CA+XidOHts1w1qR52BE=w5as-Z81=ROe_wD6r-L4PcCsGDqA32A@mail.gmail.com>
MIME-Version: 1.0

On Tuesday, 30 June 2026 12:00:05 Central European Summer Time Ben Cooksley=
=20
wrote:
> On Sat, Jun 27, 2026 at 8:17=E2=80=AFPM Volker Krause <[email protected]> w=
rote:
> > On Donnerstag, 25. Juni 2026 12:00:31 Mitteleurop=C3=A4ische Sommerzeit=
 Ben
> >=20
> > Cooksley wrote:
> > > > kalarm - 2nd week
> > > >=20
> > > >  * https://invent.kde.org/pim/kalarm/-/pipelines/1271931
> > > > =20
> > > >   * craft windows job timed out
> > > >=20
> > > > kontact - 2nd week
> > > >=20
> > > >  * https://invent.kde.org/pim/kontact/-/pipelines/1273055
> > > >  * https://invent.kde.org/pim/kontact/-/pipelines/1271145 (stable)
> > > > =20
> > > >   * craft windows job ran out of memory
> > >=20
> > > Given the Craft jobs for both Kontact and KAlarm both rely on building
> >=20
> > the
> >=20
> > > entire PIM stack from scratch (due to the master requirement) i'm not
> >=20
> > sure
> >=20
> > > if keeping these builds is sustainable.
> > > Building all the PIM stack pieces takes the CI nodes the better part =
of
> >=20
> > 40
> >=20
> > > minutes or so (including signing) and we don't yet have a solution to
> >=20
> > avoid
> >=20
> > > that as far as i'm aware.
> > >=20
> > > Can anyone from PIM comment as to whether other options are possible?
> >=20
> > Kontact is heavy, in the same league as other large applications
> > struggling
> > with the 1h limit. The obvious optimizations (no tests, unity builds, e=
tc)
> > seem already be exhausted.
>=20
> *nod*. Something that will need to be worked through - aside from Kontact
> the only other application i'm aware of hitting this limit lately is
> Kdenlive?
>=20
> > 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/=
157
> > 7
> > still.
> >=20
> > This wont really help with the most heavy parts though, things like
> > messagelib
> > are essentially KMail.
>=20
> Makes sense.
>=20
> 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 to
> build.
> Don't suppose it would be easy to break those up into smaller, less
> problematic pieces?
>=20
> 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), which I would lik=
e=20
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 consistentl=
y=20
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 lar=
ge=20
(1k lines), but contains some compile-time computation magic behind the=20
harmless looking macros. Breaking this up is not entirely impossible either=
,=20
but it would be rather inconvenient as those files are more or less a 1:1=20
translation of official specifications and match their structure.

Instead I would (again) suggest to disable the itinerary plugin for KMail o=
n=20
Windows, which is the only reason this is built. As Itinerary itself isn't=
=20
available for Windows and as the KDE Connect integration in the plugin is n=
ot=20
compatible with KDE Connect on Windows, two thirds of its functionality are=
=20
not available there anyway.

Ie. revert https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/
4507061e1323a346598382b226e3f562c6638eb3.

Best regards,
Volker
--nextPart7FnrksZtQwyIUzv_qTJLsQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iHkEABECADkWIQQAnu3FVHA48KjZ07R/lszWTRLSRwUCakP0vhsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMSwyLDIACgkQf5bM1k0S0kemzgCghn7+O+E3NYo+8k2T3drc
FksMQIQAoKQtVfIwuJKwlvev6V5nEqEVPuWx
=BNsY
-----END PGP SIGNATURE-----

--nextPart7FnrksZtQwyIUzv_qTJLsQ--