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

--nextPartMsxAe_b4TgCRh7b9-JmKzQ
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: Sat, 27 Jun 2026 09:45:01 +0200
Message-ID: <[email protected]>
Organization: KDE
In-Reply-To:  <CA+XidOERLOV5XtETOfg5o5BLV0Q0NCMCywjrYFKaB_crqBHV0Q@mail.gmail.com>
MIME-Version: 1.0

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 the
> entire PIM stack from scratch (due to the master requirement) i'm not sure
> if keeping these builds is sustainable.
> Building all the PIM stack pieces takes the CI nodes the better part of 40
> minutes or so (including signing) and we don't yet have a solution to avo=
id
> that as far as i'm aware.
>=20
> Can anyone from PIM comment as to whether other options are possible?

Kontact is heavy, in the same league as other large applications struggling=
=20
with the 1h limit. The obvious optimizations (no tests, unity builds, etc)=
=20
seem already be exhausted.

Moving more libraries to Frameworks helps a tiny bit, but that is a very sl=
ow=20
process.  We have just done that with KMime, the full impact on Craft isn't=
=20
there yet though, needs at least https://invent.kde.org/packaging/craft-blu=
eprints-kde/-/merge_requests/1577 still.

This wont really help with the most heavy parts though, things like message=
lib=20
are essentially KMail.

KAlarm OTOH shouldn't be that heavy for Windows, see https://invent.kde.org/
packaging/craft-blueprints-kde/-/merge_requests/1579 for a suggested=20
improvement.

Regards,
Volker
--nextPartMsxAe_b4TgCRh7b9-JmKzQ
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/lszWTRLSRwUCaj9/fRsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMSwyLDIACgkQf5bM1k0S0kdNTgCggdwdd0NJV3Jt7Y93cXi1
3eULBUAAmwZLd52JjzpSdaypoTCFHuQdzJlo
=gkdd
-----END PGP SIGNATURE-----

--nextPartMsxAe_b4TgCRh7b9-JmKzQ--