[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-frameworks-devel
Subject:    Re: KDE Frameworks with failing CI (master) (7 April 2024)
From:       Volker Krause <vkrause () kde ! org>
Date:       2024-04-09 16:33:04
Message-ID: 12424839.O9o76ZdvQC () vkpc5
[Download RAW message or body]


On Sonntag, 7. April 2024 23:02:06 CEST Albert Astals Cid 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.
> 
> Bad news: 3 repositories have started failing
> 
> kconfigwidgets - NEW
>  * https://invent.kde.org/frameworks/kconfigwidgets/-/pipelines/655246
>   * klanguagenametest fails in Linux
>    * https://invent.kde.org/frameworks/kconfigwidgets/-/merge_requests/234
> 
> 
> kcontacts - NEW
>  * https://invent.kde.org/frameworks/kcontacts/-/pipelines/655247
>   * AddressTest::formatTest fails in FreeBSD

That's the same issue that also hit kitinerary. As I haven't gotten any 
answers for my questions about what changed on the CI there I've now disabled 
this test for FreeBSD for kitinerary, I can do the same for KContacts I guess.

> kuserfeedback - NEW
>  * https://invent.kde.org/frameworks/kuserfeedback/-/pipelines/655248
>   * The code requires unreleased versions so flatpak fails

Hm, that's a systematic problem: We cannot do Flatpak builds in a KF master 
branch on top of an existing runtime.

Doing Flatpak builds only in the stable branch wont work here given there is 
no such branch. So the options I can think of are either building all KF 
dependencies explicitly here rather than using those from the runtime, or 
splitting the management/analytics tools (which is what the Flatpak is 
actually for) from the library.

Regards,
Volker
["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]