On Sat, Jun 27, 2026 at 8:17 PM Volker Krause <[email protected]> wrote:
> 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. > *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? > > 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. > 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 to 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. > > KAlarm OTOH shouldn't be that heavy for Windows, see > https://invent.kde.org/ > packaging/craft-blueprints-kde/-/merge_requests/1579 > <https://invent.kde.org/packaging/craft-blueprints-kde/-/merge_requests/1579> > for a suggested > improvement. > Yes there do seem to be parts of PIM that unnecessarily have CD jobs running on them, and removing unneeded deps helps. > > Regards, > Volker Cheers, Ben
