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

[Volker Krause]

On Donnerstag, 25. Juni 2026 12:00:31 Mitteleuropäische Sommerzeit 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 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 avoid
> that as far as i'm aware.
> 
> Can anyone from PIM comment as to whether other options are possible?

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.

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/1577 still.

This wont really help with the most heavy parts though, things like messagelib 
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 
improvement.

Regards,
Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 232 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20260627/48caafb0/attachment.sig>