Re: kcm_bluetooth changed ?
On 2022/2/13 05:46, Martin Koller wrote: What has changed and how would I now use the new KCM in a KCMultiDialog ? It can be changed to "kcm_bluetooth". Please see [1] to see if that helps. [1] https://invent.kde.org/plasma/bluedevil/-/merge_requests/49
KDE CI: Frameworks » knewstuff » kf5-qt5 SUSEQt5.15 - Build # 435 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/knewstuff/job/kf5-qt5%20SUSEQt5.15/435/ Project: kf5-qt5 SUSEQt5.15 Date of build: Sun, 13 Feb 2022 01:39:37 + Build duration: 3 min 16 sec and counting BUILD ARTIFACTS acc/KF5NewStuff-5.91.0.xml JUnit Tests Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: projectroot.autotests Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report47% (8/17)33% (28/84)33% (28/84)25% (2117/8365)15% (1944/13217)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests100% (1/1)100% (1/1)100% (58/58)53% (33/62)autotests.core100% (3/3)100% (3/3)99% (187/189)52% (100/192)autotests.kmoretools50% (1/2)50% (1/2)73% (225/307)47% (109/234)src20% (2/10)20% (2/10)4% (22/550)0% (0/153)src.attica0% (0/2)0% (0/2)0% (0/418)0% (0/1349)src.core56% (14/25)56% (14/25)35% (996/2883)18% (1307/7282)src.core.jobs43% (3/7)43% (3/7)20% (63/309)5% (32/649)src.kmoretools60% (3/5)60% (3/5)48% (433/902)33% (156/472)src.opds0% (0/1)0% (0/1)0% (0/336)0% (0/1120)src.qtquick0% (0/12)0% (0/12)0% (0/924)0% (0/468)src.staticxml100% (1/1)100% (1/1)67% (133/199)33% (207/636)src.tools.knewstuff-dialog0% (0/2)0% (0/2)0% (0/84)0% (0/35)src.ui0% (0/8)0% (0/8)0% (0/781)0% (0/317)src.upload0% (0/1)0% (0/1)0% (0/124)0% (0/154)src.widgets0% (0/2)0% (0/2)0% (0/61)0% (0/18)tests0% (0/1)0% (0/1)0% (0/98)0% (0/48)tests.kmoretools0% (0/1)0% (0/1)0% (0/142)0% (0/28)
kcm_bluetooth changed ?
Hi,
in liquidshell I start the bluetooth KCM via:
dialog = new KCMultiDialog(this);
KCModuleInfo module("bluetooth");
if ( module.service() )
dialog->addModule("bluetooth");
this worked until the latest update to 5.24.0
(working means: the KCM content appeared inside the dialog. Now the dialog
is empty and no bluetooth content can be seen)
What has changed and how would I now use the new KCM in a KCMultiDialog ?
--
Best regards/Schöne Grüße
Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
() ascii ribbon campaign - against html e-mail
/\- against proprietary attachments
Frühstück, Geschenkideen, Accessoires, Kulinarisches: www.lillehus.at
Re: Dropping dead(?) Python bindings generation code?
On Sun, Feb 13, 2022 at 6:36 AM Friedrich W. H. Kossebau wrote: > Hi, > Hi there, > > trying to ensure some changes do not break the Python binding generation, > I > actually tried to activate that, but found at least on current openSUSE TW > there seem to be no longer any working dependencies. Also the openSUSE TW > packages of the KF modules seem to also be build without bindings, for the > samples I checked. > > Then I found that on both gitlab & jenkins CI the binding generation is > also > skipt (at least for KCoreAddons on all platforms, but seems also > everywhere > else). > Some related commit removing the support talks about "deterministic" > builds > though: > https://invent.kde.org/sysadmin/ci-tooling/-/commit/ > 6a92fdf747990d2e074e92b2bdc224efc9b08740 > Not sure if SUSE hit the same issues we did, but the build of these on KDE CI has been disabled for a long time because the Python bindings did not build reliably. This was caused by dependency sequencing issues from my understanding within CMake. Consequently we would get builds falling over periodically for no reason other than the timing within the build itself. This usually made it pretty difficult for Dependency Builds to complete as at least one Framework would invariably fall over. Without that being fixed, we would continue to have the Python bindings support disabled on the CI system regardless of anything else being fixed. > > Then on #kde-devel I was told that"pyqt5 5.15.6 + sip4" do no more go > together, referencing > https://www.riverbankcomputing.com/pipermail/pyqt/2021-November/044346.html > : > > It wasn't an intentional breakage but it's not something I'm going to > rush > to fix. > > Who feels in charge of the Python binding support? Is there a chance > someone > will work on this soonish? > > Or could we drop it now, and save everyone the cmake warning messages they > cannot fix and also the bad feeling to change things that might break > binding > generation support even further? > > It was suggested that "the only reasonable way forward it to port to > modern > sip" "but that requires an almost full rewrite". > Which sounds as if any future system will need a rework of ECM's > PythonModuleGeneration as well, thus keeping the current CMake code in KF > modules around in chance they might get used again as they are in the > future > would not make sense. > > Reference removal of the Python binding generation support up as > https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/198 > to serve as example for the discussion. > > Cheers > Friedrich > Cheers, Ben
Dropping dead(?) Python bindings generation code?
Hi, trying to ensure some changes do not break the Python binding generation, I actually tried to activate that, but found at least on current openSUSE TW there seem to be no longer any working dependencies. Also the openSUSE TW packages of the KF modules seem to also be build without bindings, for the samples I checked. Then I found that on both gitlab & jenkins CI the binding generation is also skipt (at least for KCoreAddons on all platforms, but seems also everywhere else). Some related commit removing the support talks about "deterministic" builds though: https://invent.kde.org/sysadmin/ci-tooling/-/commit/ 6a92fdf747990d2e074e92b2bdc224efc9b08740 Then on #kde-devel I was told that"pyqt5 5.15.6 + sip4" do no more go together, referencing https://www.riverbankcomputing.com/pipermail/pyqt/2021-November/044346.html: > It wasn't an intentional breakage but it's not something I'm going to rush to fix. Who feels in charge of the Python binding support? Is there a chance someone will work on this soonish? Or could we drop it now, and save everyone the cmake warning messages they cannot fix and also the bad feeling to change things that might break binding generation support even further? It was suggested that "the only reasonable way forward it to port to modern sip" "but that requires an almost full rewrite". Which sounds as if any future system will need a rework of ECM's PythonModuleGeneration as well, thus keeping the current CMake code in KF modules around in chance they might get used again as they are in the future would not make sense. Reference removal of the Python binding generation support up as https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/198 to serve as example for the discussion. Cheers Friedrich
Re: Urgent Kirigami issue (Fwd: Re: 3 respins for 5.91.0)
This should be fixed on master actually with https://invent.kde.org/frameworks/ kirigami/-/commit/321b49a8fc1c9fa936400713f271e590a3914b27 . Though I think I forgot to mention that it is needed, sorry about that. - Arjen On Saturday, 12 February 2022 15:03:03 CET David Faure wrote: > -- Forwarded Message -- > > Subject: Re: 3 respins for 5.91.0 > Date: samedi 12 février 2022, 12:48:15 CET > From: Tobias C. Berner > To: David Faure > > Moin moin > > kirigami2 seems to fail with ninja now: > > CMake Error: > Running > > '/usr/local/bin/ninja' '-C' > '/wrkdirs/usr/ports/x11-toolkits/kf5-kirigami2/work/.build' '-t' > 'recompact' > > failed with: > > ninja: error: build.ninja:1504: multiple rules generate > src/org/kde/kirigami.2/swipenavigator/PageTab.qml [ > -w dupbuild=err] > > > mfg Tobias > > On Sat, 12 Feb 2022 at 11:04, David Faure wrote: > > Many severe bugs found and fixed this week... > > > > kirigami v5.91.0-rc3 > > e44ad90a733b476fda87ce9dec462c118911ed2e > > 083204c5f3d12fc85e24d0e1763c935120efcf6d69482bd9e19b0e97bf8822a3 sources/ > > kirigami2-5.91.0.tar.xz > > > due to https://invent.kde.org/frameworks/kirigami/-/merge_requests/ > > 494#note_396227 > > > kio v5.91.0-rc2 > > 7571449b2fb5b960db693de443fe319bb76c4f8b > > f2ddea299f3dc98835df445dd1d622d90233115ad0200e75da5e954523466293 sources/ > > kio-5.91.0.tar.xz > > > due to https://invent.kde.org/frameworks/kio/-/merge_requests/ > > 752#note_396030 > > > knewstuff v5.91.0-rc2 > > 2a1129c5686f5c278cd661532265531da8550ead > > 5dd9fb32fe7e99b64f8dc4b8801bbdba5dc5ba2eda9bec2fb1fc563a53ec6a2a sources/ > > knewstuff-5.91.0.tar.xz > > > due to https://marc.info/?l=kde-frameworks-devel&m=164445401017044&w=2 > > > > Thanks for updating the packages. I'll make the tarballs public > > in 8 hours or so, to give you time to do that. > > > > -- > > David Faure, fa...@kde.org, http://www.davidfaure.fr > > Working on KDE Frameworks 5 > > -
Urgent Kirigami issue (Fwd: Re: 3 respins for 5.91.0)
-- Forwarded Message -- Subject: Re: 3 respins for 5.91.0 Date: samedi 12 février 2022, 12:48:15 CET From: Tobias C. Berner To: David Faure Moin moin kirigami2 seems to fail with ninja now: CMake Error: Running '/usr/local/bin/ninja' '-C' '/wrkdirs/usr/ports/x11-toolkits/kf5-kirigami2/work/.build' '-t' 'recompact' failed with: ninja: error: build.ninja:1504: multiple rules generate src/org/kde/kirigami.2/swipenavigator/PageTab.qml [ -w dupbuild=err] mfg Tobias On Sat, 12 Feb 2022 at 11:04, David Faure wrote: > > Many severe bugs found and fixed this week... > > kirigami v5.91.0-rc3 > e44ad90a733b476fda87ce9dec462c118911ed2e > 083204c5f3d12fc85e24d0e1763c935120efcf6d69482bd9e19b0e97bf8822a3 sources/ kirigami2-5.91.0.tar.xz > due to https://invent.kde.org/frameworks/kirigami/-/merge_requests/ 494#note_396227 > > kio v5.91.0-rc2 > 7571449b2fb5b960db693de443fe319bb76c4f8b > f2ddea299f3dc98835df445dd1d622d90233115ad0200e75da5e954523466293 sources/ kio-5.91.0.tar.xz > due to https://invent.kde.org/frameworks/kio/-/merge_requests/ 752#note_396030 > > knewstuff v5.91.0-rc2 > 2a1129c5686f5c278cd661532265531da8550ead > 5dd9fb32fe7e99b64f8dc4b8801bbdba5dc5ba2eda9bec2fb1fc563a53ec6a2a sources/ knewstuff-5.91.0.tar.xz > due to https://marc.info/?l=kde-frameworks-devel&m=164445401017044&w=2 > > Thanks for updating the packages. I'll make the tarballs public > in 8 hours or so, to give you time to do that. > > -- > David Faure, fa...@kde.org, http://www.davidfaure.fr > Working on KDE Frameworks 5 > > > - -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5
Re: Critical Denial of Service bugs in Discover
On Fri, Feb 11, 2022 at 10:22 AM Fabian Vogt wrote: > Moin, > > Am Sonntag, 6. Februar 2022, 21:54:13 CET schrieb Fabian Vogt: > > Am Sonntag, 6. Februar 2022, 19:27:11 CET schrieb Ben Cooksley: > > > On Sun, Feb 6, 2022 at 1:07 PM Fabian Vogt > wrote: > > > > The first URL is used by kfontinst.knsrc from plasma-workspace: > > > > ProvidersUrl= > https://distribute.kde.org/khotnewstuff/fonts-providers.xml > > > > > > > > The second URL is used by multiple knsrc files in my VM: > > > > aurorae.knsrc:ProvidersUrl= > https://download.kde.org/ocs/providers.xml > > > > comic.knsrc:ProvidersUrl=https://download.kde.org/ocs/providers.xml > > > > kwineffect.knsrc:ProvidersUrl= > https://download.kde.org/ocs/providers.xml > > > > kwinscripts.knsrc:ProvidersUrl= > https://download.kde.org/ocs/providers.xml > > > > kwinswitcher.knsrc:ProvidersUrl= > https://download.kde.org/ocs/providers.xml > > > > wallpaperplugin.knsrc:ProvidersUrl= > > > > https://download.kde.org/ocs/providers.xml > > > > > > This makes me incredibly sad. We had a push to eliminate all usage of > the > > > legacy download.kde.org endpoint many years ago... > > > I have now resolved the majority of these - if distributions could > please > > > pick up those patches that would be appreciated. > > > > > > Please note that I have now terminated the support on the server that > was > > > making these legacy endpoints work, so those patches are necessary to > > > restore functionality. > > ... > > It's also possible that the requests aren't actually caused by Discover > at all, > > but just something which imitates it in a DDoS attack. In that case we > couldn't > > do anything on the client-side anyway. I don't think this is very > likely, but > > until the issue was reproduced with disover it's a possibility. > > I think I have a plausible explanation for what could've caused this. > While testing a MR for the notifier, I noticed odd behaviour: It always ran > plasma-discover-update twice! > https://invent.kde.org/plasma/discover/-/merge_requests/254#note_394584 > > The reason for that is that after the update process finishes, the notifier > realizes that it's idle again and if updates are available, it will > immediately > trigger another update after the 15min idle time. Now here's the catch: If > the > system has already been idle for >=15min (which is very likely at that > point), > the idle timeout will immediately fire! This process repeats unlimited and > without delay, until the system is no longer idle or there aren't updates > available anymore. Here I have plasma-discover-update running approx. every > second, which amounts to ~4 req/s to download.kde.org. > > This is mostly mitigated by the introduction of the 3h delay between > updates > by d607e0c6f9, but not entirely. The check is only effective after the > second > iteration, which is what I observed in my testing. (One of the commits in > my MR > should address that as well.) > > One of the conditions for running into this bug is that after the automatic > updater ran, there still have to be updates available to trigger the next > run. > Initially I thought that this can mostly happen if updates fail to > download or > install, this is unfortunately not true. The notifier by default counts all > available updates, but the updater only installs offline updates. So if > there > is even a single non-offline update available, the loop continues. > Continues infinitely I assume? > > So this probably affected a lot of users who enabled automatic > installation of > updates :-/ > Do we know if any distributions flipped that switch? > > Cheers, > Fabian > > Regards, Ben
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1395 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1395/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sat, 12 Feb 2022 10:06:25 + Build duration: 3 min 48 sec and counting JUnit Tests Name: projectroot Failed: 2 test(s), Passed: 58 test(s), Skipped: 0 test(s), Total: 60 test(s)Failed: projectroot.autotests.kiocore_ktcpsockettestFailed: 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)
KDE CI: Frameworks » kio » kf5-qt5 SUSEQt5.15 - Build # 1378 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.15/1378/ Project: kf5-qt5 SUSEQt5.15 Date of build: Sat, 12 Feb 2022 10:04:06 + Build duration: 5 min 45 sec and counting BUILD ARTIFACTS acc/KF5KIO-5.91.0.xml JUnit Tests Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 1 test(s), Passed: 60 test(s), Skipped: 0 test(s), Total: 61 test(s)Failed: 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) Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report61% (25/41)69% (297/428)69% (297/428)58% (39288/67949)42% (21752/52028)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests95% (61/64)95% (61/64)91% (11400/12471)46% (7156/15598)autotests.http100% (5/5)100% (5/5)99% (527/528)58% (167/290)autotests.kcookiejar100% (1/1)100% (1/1)94% (173/185)63% (70/112)src100% (1/1)100% (1/1)89% (8/9)71% (10/14)src.core88% (107/121)88% (107/121)61% (9352/15283)52% (4618/8872)src.core.kssl100% (1/1)100% (1/1)38% (33/86)50% (2/4)src.filewidgets79% (30/38)79% (30/38)58% (5399/9377)44% (2322/5323)src.gui100% (11/11)100% (11/11)73% (867/1182)58% (458/784)src.gui.systemd50% (2/4)50% (2/4)4% (7/178)1% (1/108)src.ioslaves.file100% (7/7)100% (7/7)56% (785/1400)42% (518/1227)src.ioslaves.file.kauth0% (0/2)0% (0/2)0% (0/187)0% (0/83)src.ioslaves.ftp100% (2/2)100% (2/2)40% (551/1380)30% (435/1430)src.ioslaves.help0% (0/5)0% (0/5)0% (0/253)0% (0/138)src.ioslaves.http88% (7/8)88% (7/8)43% (1873/4354)37% (1359/3719)src.ioslaves.http.kcookiejar40% (2/5)40% (2/5)49% (664/1364)56% (588/1053)src.ioslaves.remote100% (2/2)100%
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1394 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1394/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sat, 12 Feb 2022 09:56:39 + Build duration: 9 min 34 sec 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.applicationlauncherjob_forkingtestFailed: projectroot.autotests.kiocore_ktcpsockettestFailed: 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)
KDE CI: Frameworks » kio » kf5-qt5 SUSEQt5.15 - Build # 1377 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.15/1377/ Project: kf5-qt5 SUSEQt5.15 Date of build: Sat, 12 Feb 2022 09:56:38 + Build duration: 7 min 26 sec and counting BUILD ARTIFACTS acc/KF5KIO-5.91.0.xml JUnit Tests Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 2 test(s), Passed: 59 test(s), Skipped: 0 test(s), Total: 61 test(s)Failed: projectroot.autotests.kiocore_jobtestFailed: 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) Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report61% (25/41)69% (297/428)69% (297/428)58% (39290/67948)42% (21774/52028)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests95% (61/64)95% (61/64)91% (11400/12471)46% (7170/15598)autotests.http100% (5/5)100% (5/5)99% (527/528)58% (167/290)autotests.kcookiejar100% (1/1)100% (1/1)94% (173/185)63% (70/112)src100% (1/1)100% (1/1)89% (8/9)71% (10/14)src.core88% (107/121)88% (107/121)61% (9355/15283)52% (4627/8872)src.core.kssl100% (1/1)100% (1/1)38% (33/86)50% (2/4)src.filewidgets79% (30/38)79% (30/38)58% (5403/9377)44% (2324/5323)src.gui100% (11/11)100% (11/11)73% (867/1182)58% (458/784)src.gui.systemd50% (2/4)50% (2/4)4% (7/178)1% (1/108)src.ioslaves.file100% (7/7)100% (7/7)56% (785/1400)42% (518/1227)src.ioslaves.file.kauth0% (0/2)0% (0/2)0% (0/187)0% (0/83)src.ioslaves.ftp100% (2/2)100% (2/2)40% (551/1380)30% (435/1430)src.ioslaves.help0% (0/5)0% (0/5)0% (0/253)0% (0/138)src.ioslaves.http88% (7/8)88% (7/8)43% (1873/4354)37% (1360/3719)src.ioslaves.http.kcookiejar40% (2/5)40% (2/5)49% (664/1364)56% (588/1053)src.ioslaves.remote100% (2/2)100%
KDE CI: Frameworks » extra-cmake-modules » kf5-qt5 SUSEQt5.15 - Build # 367 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20SUSEQt5.15/367/ Project: kf5-qt5 SUSEQt5.15 Date of build: Sat, 12 Feb 2022 09:55:10 + Build duration: 6 min 12 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 24 test(s), Skipped: 0 test(s), Total: 25 test(s)Failed: projectroot.tests.KDEFetchTranslationsName: projectroot.home.jenkins.workspace.Frameworks.extra-cmake-modules Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.tests Failed: 0 test(s), Passed: 76 test(s), Skipped: 0 test(s), Total: 76 test(s)Name: projectroot.tests.ECMAddTests Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s) Cobertura Report Project Coverage Summary Name Cobertura Coverage Report
KDE CI: Frameworks » extra-cmake-modules » kf5-qt5 SUSEQt5.15 - Build # 366 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20SUSEQt5.15/366/ Project: kf5-qt5 SUSEQt5.15 Date of build: Sat, 12 Feb 2022 09:49:58 + Build duration: 5 min 10 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 24 test(s), Skipped: 0 test(s), Total: 25 test(s)Failed: projectroot.tests.KDEFetchTranslationsName: projectroot.home.jenkins.workspace.Frameworks.extra-cmake-modules Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.tests Failed: 0 test(s), Passed: 76 test(s), Skipped: 0 test(s), Total: 76 test(s)Name: projectroot.tests.ECMAddTests Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s) Cobertura Report Project Coverage Summary Name Cobertura Coverage Report
KDE CI: Frameworks » extra-cmake-modules » kf5-qt5 FreeBSDQt5.15 - Build # 322 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20FreeBSDQt5.15/322/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sat, 12 Feb 2022 09:52:23 + Build duration: 2 min 25 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 24 test(s), Skipped: 0 test(s), Total: 25 test(s)Failed: projectroot.tests.KDEFetchTranslationsName: projectroot.tests Failed: 0 test(s), Passed: 66 test(s), Skipped: 0 test(s), Total: 66 test(s)Name: projectroot.tests.ECMAddTests Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)
KDE CI: Frameworks » extra-cmake-modules » kf5-qt5 FreeBSDQt5.15 - Build # 321 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20FreeBSDQt5.15/321/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sat, 12 Feb 2022 09:49:59 + Build duration: 2 min 22 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 24 test(s), Skipped: 0 test(s), Total: 25 test(s)Failed: projectroot.tests.KDEFetchTranslationsName: projectroot.tests Failed: 0 test(s), Passed: 66 test(s), Skipped: 0 test(s), Total: 66 test(s)Name: projectroot.tests.ECMAddTests Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)
