KDE Frameworks with failing CI (master) (12 April 2026)

[Ben Cooksley]

On Sun, Apr 12, 2026 at 9:59 PM Albert Astals Cid <aacid at kde.org> wrote:

> Please work on fixing them, otherwise I will remove the failing CI jobs on
> their 4th failing week, it is very important that CI is passing for
> multiple
> reasons.
>
> VERY BAD NEWS: kcontacts alpine CI was removed because it failed for 4
> consecutive weeks
>
>
> VERY BAD NEWS: ki18n alpine CI was removed because it failed for 4
> consecutive
> weeks
>
>
> VERY BAD NEWS: kquickcharts alpine CI was removed because it failed for 4
> consecutive weeks
>

These three are quite bad, would be nice if someone could please look into
these and resolve them. I'll be looking to rollout Alpine Qt 6.11 soon,
replacing our Alpine Qt 6.10 image we currently use and not having
Frameworks CI jobs in place is going to cause issues for us in the long run
- so not having this fixed will likely mean the discontinuance of the
platform in the long term.


>
>
> VERY BAD NEWS: kquickcharts suse_tumbleweed_qt610_static CI was removed
> because it failed for 4 consecutive weeks
>
>
> Bad news: 1 repo continue failing, 1 repo started failing
>
> Good news: 3 repo fixed
>
>
> ktexteditor - 2ND WEEK
>  * https://invent.kde.org/frameworks/ktexteditor/-/pipelines/1208584
>   * suse_tumbleweed_qt612: scripttester_test fails
>

Qt 6.12 regression presumably, so we can live with this for now?


>
>
> kcontacts - NEW
>  * https://invent.kde.org/frameworks/kcontacts/-/pipelines/1214589
>   * suse_tumbleweed_qt610_static fails to find LibMount
>

Seems to be fine now?


>
> Cheers,
>   Albert
>

Thanks,
Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20260413/61813e98/attachment.htm>