KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 363 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/363/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Thu, 03 Dec 2020 21:50:02 + Build duration: 3 min 58 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 57 test(s), Skipped: 0 test(s), Total: 58 test(s)Failed: projectroot.autotests.kiocore_jobtestName: 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 FreeBSDQt5.15 - Build # 362 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/362/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Thu, 03 Dec 2020 21:45:37 + Build duration: 4 min 23 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 57 test(s), Skipped: 0 test(s), Total: 58 test(s)Failed: projectroot.autotests.kiocore_jobtestName: 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 » kcoreaddons » kf5-qt5 SUSEQt5.14 - Build # 9 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kcoreaddons/job/kf5-qt5%20SUSEQt5.14/9/ Project: kf5-qt5 SUSEQt5.14 Date of build: Thu, 03 Dec 2020 20:55:26 + Build duration: 4 min 1 sec and counting BUILD ARTIFACTS abi-compatibility-results.yamlacc/KF5CoreAddons-5.77.0.xmlcompat_reports/KF5CoreAddons_compat_report.htmllogs/KF5CoreAddons/5.77.0/log.txt 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: 27 test(s), Skipped: 0 test(s), Total: 27 test(s) Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report91% (10/11)87% (84/97)87% (84/97)75% (7102/9483)42% (10843/25764)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests94% (32/34)94% (32/34)95% (3008/3181)47% (6233/13210)src.desktoptojson100% (2/2)100% (2/2)76% (94/123)37% (109/292)src.lib67% (2/3)67% (2/3)62% (393/632)28% (249/886)src.lib.caching100% (2/2)100% (2/2)45% (352/781)16% (187/1190)src.lib.io77% (10/13)77% (10/13)67% (891/1328)36% (1018/2825)src.lib.jobs71% (5/7)71% (5/7)55% (171/311)42% (59/140)src.lib.plugin100% (8/8)100% (8/8)76% (676/888)35% (872/2513)src.lib.randomness100% (3/3)100% (3/3)71% (72/101)58% (49/84)src.lib.text63% (5/8)63% (5/8)52% (444/853)47% (1036/2191)src.lib.util100% (15/15)100% (15/15)83% (1001/1200)50% (1031/2043)tests0% (0/2)0% (0/2)0% (0/85)0% (0/390)
KDE CI: Frameworks » kcoreaddons » kf5-qt5 FreeBSDQt5.15 - Build # 113 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kcoreaddons/job/kf5-qt5%20FreeBSDQt5.15/113/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Thu, 03 Dec 2020 20:55:26 + Build duration: 1 min 42 sec and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 27 test(s), Skipped: 0 test(s), Total: 27 test(s)
KDE CI: Frameworks » kxmlgui » kf5-qt5 WindowsMSVCQt5.15 - Build # 19 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kxmlgui/job/kf5-qt5%20WindowsMSVCQt5.15/19/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Thu, 03 Dec 2020 20:29:11 + Build duration: 3 min 16 sec and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s)
Re: KCGroups in KDEreview
On Thu, Dec 3, 2020 at 12:48 PM Kevin Ottens wrote: > > Good point. Got a similar question though, which other unit types would be > useful to control? Reason being that API wise I'd smell an enum for something > like this. > Well if this library would evolve towards C++ API for interacting with systemd, then the following could potentially be useful: - *.timer (cron jobs) - *.scope (confinement to a cgroup) - *.slice (resource partitioning between cgroups) - *.mount (mount options for filesystems) - *.automount (automatically activating a mount for plug and play removable storage without too much fsck risk) - *.service (managing background services) - *.socket (in case your services do things with socket based activation, e.g. dbs) Some of these are obviously already covered, but because I'm not familiar with the KCGroups code base I just listed them for the sake of completeness. Covering them all would give you the basic building block for a GUI for systemd more generally. Additionally, if the "all the wrappers included" approach is taken it might eventually also be worth considering systemd-homed (portable user directories backed by encrypted storage). Regards, - Johan Ouwerkerk
Re: KCGroups in KDEreview
Hello, On Thursday, 3 December 2020 12:15:52 CET David Edmundson wrote: > Ultimately this isn't really dealing with cgroups directly but with > the manager to control them, systemd. > > That's correct usage, kernel docs of cgroups say to go via a > controller for write operations. However that at point is it worth > naming the library ksystemd? > It might cause some contention due to people who get angsty at a name, > but it's a lot more fitting. It would then give us a place to dump a > lot of other wrappers (especially logind) that we're seeing duplicated > in a bunch of places throughout KDE. Aren't you concerned this might lead to one of our infamous dumping grounds? There's always a tension between making it too focused and tiny or unfocused and with blackhole mass... we'd need to find where it stands but "systemd wrappers" looks too loosely defined to me. Do we have a list of the wrappers you got in mind and which piece of feature they all provide? > I think we've artificially limited the usage of the library. > The code is very generic for handling units, but all the names and one > tiny line limit it to only managing a subset of units. > > If we make the "glob" static used in KApplicationScopeLister's have a > public setter (or a protected virtual) we can rename this class and it > becomes a much more generic library for others to use outside of any > initial use-case. Good point. Got a similar question though, which other unit types would be useful to control? Reason being that API wise I'd smell an enum for something like this. Regards. -- Kevin Ottens, http://ervin.ipsquad.net signature.asc Description: This is a digitally signed message part.
KDE CI: Frameworks » kcoreaddons » kf5-qt5 SUSEQt5.14 - Build # 8 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kcoreaddons/job/kf5-qt5%20SUSEQt5.14/8/ Project: kf5-qt5 SUSEQt5.14 Date of build: Thu, 03 Dec 2020 11:32:23 + Build duration: 3 min 23 sec and counting BUILD ARTIFACTS abi-compatibility-results.yamlacc/KF5CoreAddons-5.77.0.xmlcompat_reports/KF5CoreAddons_compat_report.htmllogs/KF5CoreAddons/5.77.0/log.txt 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: 26 test(s), Skipped: 0 test(s), Total: 27 test(s)Failed: projectroot.autotests.ktexttohtmltest Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report91% (10/11)81% (79/97)81% (79/97)68% (6452/9480)37% (9380/25640)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests91% (31/34)91% (31/34)84% (2681/3176)42% (5607/13210)src.desktoptojson100% (2/2)100% (2/2)76% (94/123)37% (109/292)src.lib67% (2/3)67% (2/3)62% (393/632)28% (249/886)src.lib.caching100% (2/2)100% (2/2)45% (352/781)16% (187/1190)src.lib.io77% (10/13)77% (10/13)67% (891/1328)36% (1019/2825)src.lib.jobs71% (5/7)71% (5/7)55% (171/311)42% (59/140)src.lib.plugin100% (8/8)100% (8/8)76% (676/888)35% (872/2513)src.lib.randomness100% (3/3)100% (3/3)71% (72/101)58% (49/84)src.lib.text13% (1/8)13% (1/8)14% (121/855)10% (198/2067)src.lib.util100% (15/15)100% (15/15)83% (1001/1200)50% (1031/2043)tests0% (0/2)0% (0/2)0% (0/85)0% (0/390)
KDE CI: Frameworks » kcoreaddons » kf5-qt5 FreeBSDQt5.15 - Build # 112 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kcoreaddons/job/kf5-qt5%20FreeBSDQt5.15/112/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Thu, 03 Dec 2020 11:32:23 + Build duration: 1 min 30 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 26 test(s), Skipped: 0 test(s), Total: 27 test(s)Failed: projectroot.autotests.ktexttohtmltest
Re: KCGroups in KDEreview
Ultimately this isn't really dealing with cgroups directly but with the manager to control them, systemd. That's correct usage, kernel docs of cgroups say to go via a controller for write operations. However that at point is it worth naming the library ksystemd? It might cause some contention due to people who get angsty at a name, but it's a lot more fitting. It would then give us a place to dump a lot of other wrappers (especially logind) that we're seeing duplicated in a bunch of places throughout KDE. --- I think we've artificially limited the usage of the library. The code is very generic for handling units, but all the names and one tiny line limit it to only managing a subset of units. If we make the "glob" static used in KApplicationScopeLister's have a public setter (or a protected virtual) we can rename this class and it becomes a much more generic library for others to use outside of any initial use-case. David
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 361 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/361/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Thu, 03 Dec 2020 09:59:38 + Build duration: 4 min 37 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 57 test(s), Skipped: 0 test(s), Total: 58 test(s)Failed: projectroot.autotests.kiocore_jobtestName: 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 FreeBSDQt5.15 - Build # 360 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/360/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Thu, 03 Dec 2020 09:49:03 + Build duration: 10 min and counting JUnit Tests Name: projectroot Failed: 2 test(s), Passed: 56 test(s), Skipped: 0 test(s), Total: 58 test(s)Failed: projectroot.autotests.kiocore_jobtestFailed: projectroot.autotests.kiogui_openurljobtestName: 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)
