KDE Gear projects with failing CI (master + stable) (6 October 2026)

[Christoph Cullmann]

Hi,

On Wednesday, October 7th, 2026 at 13:42, Nicolas Fella <nicolas.fella at gmx.de> wrote:

> On 07/10/2026 00:12, Christoph Cullmann wrote:
> > Hi,
> >
> >> kate - NEW
> >>   * https://invent.kde.org/utilities/kate/-/pipelines/1371568
> >>   * https://invent.kde.org/utilities/kate/-/pipelines/1365906 (stable)
> >>    * Qt 6.13 job reports leaks
> > I see no way to fix the KSelectAction leaks, locally even valgrind reports zero leaks.
> >
> > Is there a way to have that atm blacklisted in the CI to get some passing CI somewhere?
> This looks like a genuine regression in Qt dev. We shouldn't work around
> it without understanding it.

I don't want to workaround, I just want that atm our pipes pass.

On each merge I need now to manually check if it is fine and we get no nightly flatpak/...
since we have that new pipe, that makes developing a lot harder.

Could one not just disable the asan stuff until Qt has fixed that upstream?

Greetings
Christoph

> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 343 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20261007/d485900d/attachment.sig>