[sysadmin/ci-tooling] local-metadata: Re-enable Alkimia CI on Windows now that the hard dependency issues have been resolved.
Git commit 9ef1b7c455e1eeba332593eb8cd3e722bca1d33a by Ben Cooksley. Committed on 10/03/2022 at 08:42. Pushed by bcooksley into branch 'master'. Re-enable Alkimia CI on Windows now that the hard dependency issues have been resolved. CCMAIL: kde-frameworks-devel@kde.org CCMAIL: kmymoney-de...@kde.org M +0-1local-metadata/project-ignore-rules.yaml https://invent.kde.org/sysadmin/ci-tooling/commit/9ef1b7c455e1eeba332593eb8cd3e722bca1d33a diff --git a/local-metadata/project-ignore-rules.yaml b/local-metadata/project-ignore-rules.yaml index e42d203..5d7ecfd 100644 --- a/local-metadata/project-ignore-rules.yaml +++ b/local-metadata/project-ignore-rules.yaml @@ -22,7 +22,6 @@ - 'kde/workspace/libksysguard' - 'kde/kdenetwork/kaccounts-integration' - 'extragear/libs/pulseaudio-qt' -- 'extragear/office/alkimia' - "kde/pim/libkleo" 'FreeBSDQt5.15':
Re: Hard dependency on plasma-framework in Alkimia
On Thu, Mar 10, 2022 at 9:12 AM Thomas Baumgart wrote: > Hi Ben, > Hi Thomas, > > On Mittwoch, 9. März 2022 11:09:53 CET Ben Cooksley wrote: > > > Hi Thomas, > > > > Recently some changes were introduced to Frameworks which means that they > > now enforce more rigorously the platforms on which they build. > > > > This means that Plasma Framework is no longer available on Windows - > > unfortunately though it looks like Alkimia has a mandatory dependency on > > Plasma Framework. > > > > Are you able to make this optional or should we disable Windows CI builds > > for Alkimia (and the projects that depend on it)? > > I just accepted https://invent.kde.org/office/alkimia/-/merge_requests/17 > so you > can re-enable Alkimia builds once this is merged. > Thanks for getting that merged in. > > p.s. quite a short time frame from notice until cut-off for my taste. > That was a temporary measure only as I wanted to make sure there weren't any other issues in other projects that also needed addressing. I wanted to get this sorted as soon as reasonably possible to allow for progress to be made on Windows CI on Gitlab. > > -- > > Regards > > Thomas Baumgart > > https://www.signal.org/ Signal, the better WhatsApp > - > Linux, because rebooting is for adding new hardware ... > - > Cheers, Ben
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1454 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1454/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Fri, 11 Mar 2022 01:52:01 + Build duration: 12 min and counting JUnit Tests Name: projectroot Failed: 3 test(s), Passed: 57 test(s), Skipped: 0 test(s), Total: 60 test(s)Failed: projectroot.autotests.kiocore_ktcpsockettestFailed: projectroot.autotests.kiogui_openurljobtestFailed: projectroot.autotests.kiowidgets_kdirlistertestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
