KDE CI: Frameworks » kio » kf5-qt5 SUSEQt5.15 - Build # 1500 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.15/1500/ Project: kf5-qt5 SUSEQt5.15 Date of build: Fri, 15 Apr 2022 01:43:08 + Build duration: 25 min and counting BUILD ARTIFACTS acc/KF5KIO-5.94.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: 61 test(s), Skipped: 0 test(s), Total: 62 test(s)Failed: projectroot.autotests.kiocore_krecentdocumenttestName: 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)70% (300/431)70% (300/431)58% (39692/68487)42% (22092/52664)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests95% (62/65)95% (62/65)91% (11478/12575)46% (7278/15914)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)62% (9591/15554)53% (4822/9157)src.core.kssl100% (1/1)100% (1/1)38% (33/86)50% (2/4)src.filewidgets79% (31/39)79% (31/39)58% (5414/9407)44% (2308/5288)src.gui100% (12/12)100% (12/12)73% (945/1302)58% (492/844)src.gui.systemd50% (2/4)50% (2/4)4% (7/178)1% (1/108)src.ioslaves.file100% (7/7)100% (7/7)56% (780/1400)42% (513/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% (549/1378)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 » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1514 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1514/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Fri, 15 Apr 2022 01:43:08 + Build duration: 6 min 20 sec and counting JUnit Tests 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.kiocore_krecentdocumenttestName: 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 » plasma-framework » kf5-qt5 SUSEQt5.15 - Build # 900 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/plasma-framework/job/kf5-qt5%20SUSEQt5.15/900/ Project: kf5-qt5 SUSEQt5.15 Date of build: Thu, 14 Apr 2022 14:59:49 + Build duration: 2 min 22 sec and counting BUILD ARTIFACTS acc/KF5PlasmaQuick-5.94.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: 3 test(s), Passed: 8 test(s), Skipped: 0 test(s), Total: 11 test(s)Failed: projectroot.autotests.plasma_dialogqmltestFailed: projectroot.autotests.plasma_dialogstatetestFailed: projectroot.autotests.plasma_framesvgtest Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report44% (8/18)32% (39/123)32% (39/123)34% (4844/14073)26% (2364/9268)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests67% (8/12)67% (8/12)84% (817/976)45% (436/962)src.declarativeimports.calendar0% (0/6)0% (0/6)0% (0/526)0% (0/229)src.declarativeimports.core44% (7/16)44% (7/16)34% (867/2534)26% (381/1457)src.declarativeimports.kirigamiplasmastyle0% (0/2)0% (0/2)0% (0/25)0% (0/20)src.declarativeimports.plasmacomponents0% (0/6)0% (0/6)0% (0/531)0% (0/197)src.declarativeimports.plasmaextracomponents0% (0/3)0% (0/3)0% (0/42)0% (0/16)src.declarativeimports.platformcomponents0% (0/3)0% (0/3)0% (0/59)0% (0/14)src.declarativeimports.platformcomponents.utils0% (0/2)0% (0/2)0% (0/15)0% (0/2)src.plasma40% (8/20)40% (8/20)43% (1673/3875)33% (895/2719)src.plasma.packagestructure43% (3/7)43% (3/7)43% (58/135)47% (16/34)src.plasma.private41% (7/17)41% (7/17)51% (903/1778)37% (358/975)src.plasma.scripting33% (1/3)33% (1/3)12% (21/175)7% (7/105)src.plasmapkg0% (0/1)0% (0/1)0% (0/49)0% (0/42)src.plasmaquick31% (4/13)31% (4/13)24% (474/1963)17% (266/1542)src.plasmaquick.private100% (1/1)100% (1/1)78% (31/40)50% (5/10)src.scriptengines.qml.plasmoid0% (0/7)0% (0/7)0% (0/1266)0%
KDE CI: Frameworks » plasma-framework » kf5-qt5 FreeBSDQt5.15 - Build # 886 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/plasma-framework/job/kf5-qt5%20FreeBSDQt5.15/886/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Thu, 14 Apr 2022 14:56:59 + Build duration: 4 min 27 sec and counting JUnit Tests Name: projectroot Failed: 2 test(s), Passed: 9 test(s), Skipped: 0 test(s), Total: 11 test(s)Failed: projectroot.autotests.plasma_dialogqmltestFailed: projectroot.autotests.plasma_dialogstatetest
KDE CI: Frameworks » plasma-framework » kf5-qt5 SUSEQt5.15 - Build # 899 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/plasma-framework/job/kf5-qt5%20SUSEQt5.15/899/ Project: kf5-qt5 SUSEQt5.15 Date of build: Thu, 14 Apr 2022 14:53:52 + Build duration: 5 min 56 sec and counting BUILD ARTIFACTS acc/KF5PlasmaQuick-5.94.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: 3 test(s), Passed: 8 test(s), Skipped: 0 test(s), Total: 11 test(s)Failed: projectroot.autotests.plasma_dialogqmltestFailed: projectroot.autotests.plasma_dialogstatetestFailed: projectroot.autotests.plasma_framesvgtest Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report44% (8/18)32% (39/123)32% (39/123)34% (4844/14073)26% (2364/9268)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests67% (8/12)67% (8/12)84% (817/976)45% (436/962)src.declarativeimports.calendar0% (0/6)0% (0/6)0% (0/526)0% (0/229)src.declarativeimports.core44% (7/16)44% (7/16)34% (867/2534)26% (381/1457)src.declarativeimports.kirigamiplasmastyle0% (0/2)0% (0/2)0% (0/25)0% (0/20)src.declarativeimports.plasmacomponents0% (0/6)0% (0/6)0% (0/531)0% (0/197)src.declarativeimports.plasmaextracomponents0% (0/3)0% (0/3)0% (0/42)0% (0/16)src.declarativeimports.platformcomponents0% (0/3)0% (0/3)0% (0/59)0% (0/14)src.declarativeimports.platformcomponents.utils0% (0/2)0% (0/2)0% (0/15)0% (0/2)src.plasma40% (8/20)40% (8/20)43% (1673/3875)33% (895/2719)src.plasma.packagestructure43% (3/7)43% (3/7)43% (58/135)47% (16/34)src.plasma.private41% (7/17)41% (7/17)51% (903/1778)37% (358/975)src.plasma.scripting33% (1/3)33% (1/3)12% (21/175)7% (7/105)src.plasmapkg0% (0/1)0% (0/1)0% (0/49)0% (0/42)src.plasmaquick31% (4/13)31% (4/13)24% (474/1963)17% (266/1542)src.plasmaquick.private100% (1/1)100% (1/1)78% (31/40)50% (5/10)src.scriptengines.qml.plasmoid0% (0/7)0% (0/7)0% (0/1266)0%
KDE CI: Frameworks » plasma-framework » kf5-qt5 FreeBSDQt5.15 - Build # 885 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/plasma-framework/job/kf5-qt5%20FreeBSDQt5.15/885/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Thu, 14 Apr 2022 14:53:52 + Build duration: 3 min 3 sec and counting JUnit Tests Name: projectroot Failed: 2 test(s), Passed: 9 test(s), Skipped: 0 test(s), Total: 11 test(s)Failed: projectroot.autotests.plasma_dialogqmltestFailed: projectroot.autotests.plasma_dialogstatetest
Re: RFC: Frameworks headers install location
On 12/4/22 02:17, Aleix Pol wrote:
Back when we did KF5, what we tried to do was mainly to make sure kde4
code still compiled after the big split.
I think that stanradrising how they're placed within submodules of
include/KF6 is a good idea.
The fact that headers from some repositories can be included using the
project name is more an artifact of time than a feature. Those that
are meant to be used that way (e.g. Plasma or Purpose), are already
namespaced within "include/KF*/".
Ensuring that no KF6 project brings "include/KF6" as its include
directories will be a useful cleanup.
Aleix
Thanks for the feedback.
We discussed that again in the previous KF6 meeting[1], and since there are no objections so far,
we'll go ahead and put that into motion, starting with[2].
[1]
https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/3#note_431116
[2] https://invent.kde.org/frameworks/syntax-highlighting/-/merge_requests/305
Thanks,
Ahmad Samir
On Tue, Apr 5, 2022 at 4:19 PM Ahmad Samir wrote:
Hello.
- In KF5, ECM, magically, added /usr/include/KF5/ to the CMake targets
interface include directories
(IIUC for reasons of backwards compatibility, which was necessary in the 4-5
transition era, I could
be wrong because I wasn't around at that time :))
- While building KF against Qt6, this suddenly broke building in some modules
due to #include
directives not finding the headers, as /usr/include/KF6/ didn't have the same
magic-injection
treatment as KF5
- To fix the issue, proper paths had to be added to targets interface include
directories so that
module A linking against module B will have the proper include paths to search
for headers
- The typical include dir layout for a KF module is:
/usr/include/KF*/ModuleName/{ForwardingHeaderA,headera.h}
e.g. KCMutils, #include , and /usr/include/KF5/KCMUtils added to
KCMutils target
include dirs.
- If there is a namespace, the original plan was to guard the include paths, by
making them match
the C++ namespaces, e.g.:
/usr/include/KF*/ModuleName/NameSpace/ForwardingHeaderA
/usr/include/KF*/ModuleName/namespace/headera.h
e.g. KSynatxHighlighting:
/usr/include/KF*/KSyntaxHighlighting/
/usr/include/KF*/KSyntaxHighlighting/KSyntaxHighlighting/Repository
/usr/include/KF*/KSyntaxHighlighting/ksyntaxhighlighting/repository.h
There are some issues with the namespace use-case:
- On case-insensitive and/or case-preserving filesystems (which still exist in
2022...) extra care
has to be taken so that installation actually works, as you can't have two dirs
in the same path
with the same name but different cases
- Compiler warnings when using e.g. #include
if the dir that was
installed first was ksyntaxhighlighting, and all files ended up there (and
vice-versa, e.g. if the
CamelCase dir got installed first #include
would give a warning)
- A more complicated layout
The proposal is to change the layout when there is a namespace:
- Only have one dir, /usr/include/KF*/ModuleName/NameSpace/, where all headers
(ForwadingHeaders and
lowercase.h ones) are installed
Pros:
- less complicated layout/setup (simpler CMake code)
- all KDE namespaces are CamelCase, we don't have any that are lower case
- we promote/encourage using FowardingHeaders everywhere; that's what we use in
our own code and
what the API docs advise to use
Cons:
- The case not matching when using , but as I
said above the
argument for this is mitigated by the fact that all our namespaces are CamelCase
If we agree with that change this will be for KF6 so as not to break source
compatibility for KF5.
Best regards,
Ahmad Samir
Re: KF6 meeting notes 2022-04-12
On Thursday, 14 April 2022 03:22:01 CEST Aleix Pol wrote: > Hi Volker, > Thanks a lot for the notes! It makes it easier to follow the work even > if I'm unable to join lately. > > One question, how does co-installability affect flatpak? If anything, > the environment is much more controlled so it shouldn't matter that > much (?). Right, that comment referred to the plugin-only build options, not co- installability as a whole. Think of a Dolphin Flatpak wanting to have support for dealing with compressed archives and thus needing Ark's file manager plugins. Regards, Volker > On Tue, Apr 12, 2022 at 9:24 PM Volker Krause wrote: > > https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/3 > > > > https://invent.kde.org/frameworks/kconfigwidgets/-/merge_requests/131 > > - needs review/feedback > > - interesting part is openColorScheme() in kcolorschemehelpers_p.h > > - existing benchmark in the tests shows no change > > - might not work with Plasma's accent color feature, as that uses > > kdeglobals - possible approach: store only the accent color in > > kdeglobals, next to the color scheme name, and move the colors kcm color > > mixing code for this to KColorScheme > > > > https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/ > > 3#note_425424 > > - QDesktopWidget porting details noted in the issue > > - plasma-framework builds, plasma-workspace only blocked by > > kwayland-server > > issues with the QDesktopWidget uses resolved > > - plasma-desktop's biggest issue is the kdelibs4support use in the > > date/times KCM > > > > https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/ > > 3#note_431116 > > - two people in favor on mailing list, no objections, so let's go with > > this > > > > https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/ > > 3#note_431647 > > - only two applets access KPackage this way, so impact would be quite > > minimal - let's do it > > > > Co-installability/co-usability of KIO slaves with different major versions > > - kio-extras is not going to be co-installable could be a problem for this > > - also affects previews, context menu plugins, etc > > - everything plugin related is in versioned locations, so this is actually > > co- installable > > - similar problem with Ark's file manager integration plugins > > - when transitioning those to 6 would degrade 5-based consumers > > - probably needs kio-extras to be co-installable after all > > - for cases like ark, we might want a "plugins only" build flag, in 5 > > already - also helps with Flatpak bundling > > > > next meeting: > > https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/ > > issues/4 signature.asc Description: This is a digitally signed message part.
