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

[Arjen Hiemstra]

On Monday, 13 April 2026 13:23:16 Central European Summer Time Ben Cooksley 
wrote:
> 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.

I did report this to Bart when the issue first started showing up in MRs. This 
is what seems to fail (with different calls leading to the same syscall):

> __syscall_cp_asm () at src/thread/aarch64/syscall_cp.s:28
> warning: 28	src/thread/aarch64/syscall_cp.s: No such file or directory
>   0xffff8792feb0:	str	xzr, [sp, #1024]
> Thread 39 (LWP 7578 "QDBusConnection"):
> #0  __syscall_cp_asm () at src/thread/aarch64/syscall_cp.s:28
> #1  0x0000ffff944ab554 in __syscall_cp_c (nr=<optimized out>, u=<optimized 
out>, v=<optimized out>, w=<optimized out>, x=<optimized out>, y=<optimized 
out>, z=<optimized out>) at src/thread/pthread_cancel.c:33

To me that suggests there may be something going wrong at the emulation level? 
Or maybe it's Alpine needing some features that the emulator doesn't have 
enabled?

- Arjen

> 
> > 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