KDE Gear projects with failing CI (release/25.04) (6 May 2025)

Albert Vaca Cintora albertvaka at gmail.com
Wed May 7 20:22:31 BST 2025


I've disabled kdeconnect macOS builds for the release branch. I wonder if
there's a way to never build macOS builds from release branches for KDE
Connect, to save CI resources? We don't make releases from them (we point
macOS users to download builds from master directly) so those builds are
never used.

On Tue, May 6, 2025 at 11:56 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.
>
> Bad news: 1 repositories is still failing, 4 have started failing
>
> Good news: 2 repositories have been fixed
>
> neochat - 2nd week
>  * https://invent.kde.org/network/neochat/-/pipelines/944362
>   * suse_tumbleweed_qt610 test fails
>
>
> messagelib - NEW
>  * https://invent.kde.org/pim/messagelib/-/pipelines/944358
>   * Test failures in suse builders
>
>
> kdeconnect-kde - NEW
>  * https://invent.kde.org/network/kdeconnect-kde/-/pipelines/942351
>   * macos builds fail
>
>
> kosmindoormap - NEW
>  * https://invent.kde.org/libraries/kosmindoormap/-/pipelines/942365
>   * flatpak build fails
>
>
> kjournald - NEW
>  * https://invent.kde.org/system/kjournald/-/pipelines/942386
>   * test_remotejournal fails on suse_tumbleweed_qt69
>
>
> Cheers,
>   Albert
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20250507/af50c901/attachment.htm>


More information about the kde-devel mailing list