Re: Porting notes / deprecation docs

2021-07-10 Thread Friedrich W. H. Kossebau
Am Samstag, 10. Juli 2021, 22:47:58 CEST schrieb Frederik Schwarzer:
> Hi,
> 
> On 7/10/21 7:38 PM, Friedrich W. H. Kossebau wrote:
> > Am Samstag, 10. Juli 2021, 18:00:13 CEST schrieb Frederik Schwarzer:
> >> as mentioned earlier
> > 
> > Any pointers? :)
> 
> It was discussed in the weekly BBB meetings a few weeks ago.

I see. As contributor on occasions only myself, please refer to the respective 
meeting notes some thankfully write, so one can read up on more background, 
and such a planned task ideally would be backed up by a task board entry on 
phabricator, so people can coordinate and track things about it in an async 
manner.

> >> I would like to document classes/methods/etc that
> >> are going to be deprecated during KF6 development.
> > 
> > Can you help confused-on-first-read people by explaining what "deprecated
> > during KF6 development" is referring to? Deprecated during KF5 development
> > and no longer be available in KF6? Not yet deprecated due to no existing
> > replacement, but with replacement planned in KF6?
> 
> Everything that is marked deprecated when KF6 sees the light of day.

Okay. Not a good idea IMHO. There should be a single place of information, and 
we have that already with the current KF5 API docs. I hope no-one plans to 
just remove them from the website, though, Well, then there are also the 
offline docs in QCH format as backup generated during the builds and packaged 
by good distributions ;)

> The idea is to have the APIs that are being deprecated now documented
> when those APIs (and with it the API docs) are removed.
> The audience is everyone who is starting the porting work when KF6 is
> already there for some time.

Ideally that audience should get the recommendation to first port away from 
deprecated API using the last released version of KF5 and Qt6. That way they 
are able to do a big chunk of the work while being able to maintain a fully 
working state of their software, without serious regressions. Once that 
checkpoint is reached, then go for porting all those things which disappeared/
changed in KF6 & Qt6 without any preparations in KF5 & Qt5.

Remember that this is not just KF 5 -> 6, but also Qt 5 -> 6. And perhaps even 
C++11 -> C++17. IMHO only those would recommend to port directly from one set 
of APIs to an other one without any intermediate checkppints for the working 
sate of the software who want to secure their job for a while, because it will 
take ages to fix all the regressions introduced during the port. Unless the 
company/community goes down in the meantime, because the ported software does 
not get done.

BTW, even the Qt Company recommends that step-by-step approach, and they 
surely do want to have their customers be successful in a short time ;) ->
https://doc.qt.io/qt-6/portingguide.html

That is also why some of us invested so much of our time into properly tagging 
API with deprecations warning macros and visibility guards, so porting can be 
done step by step away from the old AP assisted by the compiler, always having 
a working software. Because we have been through some porting in KDE and 
learned our lessons, haven't we... ;)

> Yes it is manual work. However, since the documentation does not remove
> stuff that has been removed from the API, it's a thing of adding newer
> deprecation markers, which seems manageable.

While perhaps it might be a nice thing to have a shortcut list of API that is 
deprecated in KF5 times, as a manifest to look-up things, ideally we find ways 
to auto-generate that from the existing API markup.

After all KDE is a software developing community, so we should be able to 
automate that, no? ;)

So, I can only really ask to keep documentation of KF5's deprecated API in one 
place, and do it properly there, with nice examples, already now useful to 
those who port away when they can. And that place should be the current KF5 
API docs.
Even more as people come and go, and having yet another place which needs to 
be kept even more manually up-tod-ate does not improve things, it adds more 
risk to have outdated unmaintained information. As you could see in review, it 
already now needs poking in every second review to have proper documentation. 
And then also do that in some separate content?

What would be very good to have though IMHO, are preparations of the porting 
documentation of that API which is not deprecated in KF5, but will be replaced 
by something else in KF6 (because it cannot be done earlier for reasons). The 
KF6 task board should have some data about such plans.
Such documentation will need a place and a structure, so also need someone to 
work on and prepare it, so developers can put in the data once those 
replacements are created during KF6 init phase.

My 2 cents

Cheers
Friedrich




KDE CI: Frameworks » kio » kf5-qt5 SUSEQt5.15 - Build # 911 - Still Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.15/911/
 Project:
kf5-qt5 SUSEQt5.15
 Date of build:
Sat, 10 Jul 2021 19:27:13 +
 Build duration:
2 hr 9 min and counting
   BUILD ARTIFACTS
  acc/KF5KIO-5.85.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: 58 test(s), Skipped: 0 test(s), Total: 60 test(s)Failed: projectroot.autotests.kiocore_kprotocolinfotestFailed: projectroot.autotests.kiofilewidgets_kurlnavigatortestName: 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 Report68%
(25/37)68%
(291/425)68%
(291/425)58%
(38513/66835)41%
(21193/51115)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests94%
(59/63)94%
(59/63)90%
(10900/12164)45%
(6771/15177)autotests.http100%
(5/5)100%
(5/5)99%
(524/525)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%
(9410/15162)52%
(4664/8884)src.core.kssl100%
(1/1)100%
(1/1)39%
(34/87)50%
(3/6)src.filewidgets79%
(30/38)79%
(30/38)57%
(5181/9016)43%
(2199/5070)src.gui100%
(9/9)100%
(9/9)78%
(764/979)59%
(395/672)src.gui.systemd50%
(2/4)50%
(2/4)4%
(7/177)1%
(1/108)src.ioslaves.file100%
(7/7)100%
(7/7)57%
(792/1378)43%
(515/1190)src.ioslaves.file.kauth0%
(0/2)0%
(0/2)0%
(0/179)0%
(0/89)src.ioslaves.ftp100%
(2/2)100%
(2/2)49%
(672/1385)37%
(536/1434)src.ioslaves.help0%
(0/5)0%
(0/5)0%
(0/251)0%
(0/148)src.ioslaves.http88%
(7/8)88%
(7/8)43%
(1865/4341)37%
(1359/3719)src.ioslaves.http.kcookiejar40%
(2/5)40%
(2/5)49%
(661/1360)56%
(590/1055)src.ioslaves.remote100%

KDE CI: Frameworks » kwindowsystem » kf5-qt5 SUSEQt5.15 - Build # 96 - Fixed!

2021-07-10 Thread CI System
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kwindowsystem/job/kf5-qt5%20SUSEQt5.15/96/
 Project:
kf5-qt5 SUSEQt5.15
 Date of build:
Sat, 10 Jul 2021 19:31:24 +
 Build duration:
1 hr 59 min and counting
   BUILD ARTIFACTS
  acc/KF5WindowSystem-5.85.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: 13 test(s), Skipped: 0 test(s), Total: 13 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report67%
(4/6)78%
(43/55)78%
(43/55)74%
(7524/10161)54%
(3927/7307)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests88%
(15/17)88%
(15/17)97%
(3162/3244)52%
(1631/3142)autotests.helper100%
(1/1)100%
(1/1)73%
(8/11)50%
(3/6)src85%
(11/13)85%
(11/13)55%
(905/1652)41%
(318/768)src.platforms.wayland0%
(0/2)0%
(0/2)0%
(0/70)100%
(0/0)src.platforms.xcb94%
(16/17)94%
(16/17)70%
(3449/4913)59%
(1975/3343)tests0%
(0/5)0%
(0/5)0%
(0/271)0%
(0/48)

KDE CI: Frameworks » kwayland » kf5-qt5 FreeBSDQt5.15 - Build # 96 - Still Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20FreeBSDQt5.15/96/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sat, 10 Jul 2021 19:31:03 +
 Build duration:
1 hr 58 min and counting
   JUnit Tests
  Name: projectroot.autotests Failed: 13 test(s), Passed: 30 test(s), Skipped: 0 test(s), Total: 43 test(s)Failed: projectroot.autotests.client.kwayland_testCompositorFailed: projectroot.autotests.client.kwayland_testDataDeviceFailed: projectroot.autotests.client.kwayland_testDataSourceFailed: projectroot.autotests.client.kwayland_testIdleFailed: projectroot.autotests.client.kwayland_testRegionFailed: projectroot.autotests.client.kwayland_testShmPoolFailed: projectroot.autotests.client.kwayland_testSubCompositorFailed: projectroot.autotests.client.kwayland_testSubSurfaceFailed: projectroot.autotests.client.kwayland_testWaylandConnectionThreadFailed: projectroot.autotests.client.kwayland_testWaylandRegistryFailed: projectroot.autotests.client.kwayland_testWaylandShellFailed: projectroot.autotests.client.kwayland_testWaylandSurfaceFailed: projectroot.autotests.server.kwayland_testWaylandServerDisplay

KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 914 - Still Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/914/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sat, 10 Jul 2021 19:27:15 +
 Build duration:
2 hr 0 min and counting
   JUnit Tests
  Name: projectroot Failed: 2 test(s), Passed: 57 test(s), Skipped: 0 test(s), Total: 59 test(s)Failed: projectroot.autotests.kiocore_kprotocolinfotestFailed: projectroot.autotests.kiofilewidgets_kurlnavigatortestName: 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 » kdav » kf5-qt5 SUSEQt5.15 - Build # 70 - Fixed!

2021-07-10 Thread CI System
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kdav/job/kf5-qt5%20SUSEQt5.15/70/
 Project:
kf5-qt5 SUSEQt5.15
 Date of build:
Sat, 10 Jul 2021 19:24:02 +
 Build duration:
1 hr 43 min and counting
   BUILD ARTIFACTS
  acc/KF5DAV-5.85.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: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report75%
(3/4)67%
(33/49)67%
(33/49)46%
(1035/2254)26%
(415/1568)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests100%
(7/7)100%
(7/7)95%
(375/395)54%
(235/437)src.common63%
(24/38)63%
(24/38)39%
(574/1463)24%
(168/693)src.protocols67%
(2/3)67%
(2/3)28%
(86/302)21%
(12/58)test0%
(0/1)0%
(0/1)0%
(0/94)0%
(0/380)

Re: Porting notes / deprecation docs

2021-07-10 Thread Frederik Schwarzer

Hi,

On 7/10/21 7:38 PM, Friedrich W. H. Kossebau wrote:

Am Samstag, 10. Juli 2021, 18:00:13 CEST schrieb Frederik Schwarzer:

as mentioned earlier


Any pointers? :)


It was discussed in the weekly BBB meetings a few weeks ago.



I would like to document classes/methods/etc that
are going to be deprecated during KF6 development.


Can you help confused-on-first-read people by explaining what "deprecated
during KF6 development" is referring to? Deprecated during KF5 development and
no longer be available in KF6? Not yet deprecated due to no existing
replacement, but with replacement planned in KF6?


Everything that is marked deprecated when KF6 sees the light of day.



For that I scraped up all the deprecation macros from the frameworks and
edited them to be more unified.


That sounds like duplication of data, and worse, a manual copy of a certain
state, which also needs to be manually maintained to be up-to-date to stay
useful.

In general I am also curious what audience is targeted by the planned
documentation and in which work-flows that documentation should solve which
needs, and what other solutions are there which would not satisfy those needs
well enough?

In general, for API already deprecated now during lifetime of KF5 we are
adding porting notes to the very API itself. Which is also the place as API
consumer I would be hoping for to get all needed information straight in one
go, instead of having to jump to other places, which might even get out of
sync or focus of developers (remember that current online docs of api.kde.org
also only provide docs for latest version (and even the development one, not
just the latest released).

And this is a change to what happened in kdelibs4 times, where most
deprecation happened in the development branches for what became KDE
Frameworks, so there also was no API documentation maintained at the same
time. So copying the approach taken for the KDE Frameworks porting notes would
not be needed here 1:1 for what I understand.

Instead we would need to add documentation for those things which are again
deprecated (well, removed rather) during preparation of KF6, where the
replacement also only will be in KF6, so no-one can port before.


The idea is to have the APIs that are being deprecated now documented 
when those APIs (and with it the API docs) are removed.
The audience is everyone who is starting the porting work when KF6 is 
already there for some time.


Yes it is manual work. However, since the documentation does not remove 
stuff that has been removed from the API, it's a thing of adding newer 
deprecation markers, which seems manageable.


Do you disagree?

Cheers,
Frederik


KDE CI: Frameworks » kiconthemes » kf5-qt5 WindowsMSVCQt5.15 - Build # 91 - Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kiconthemes/job/kf5-qt5%20WindowsMSVCQt5.15/91/
 Project:
kf5-qt5 WindowsMSVCQt5.15
 Date of build:
Sat, 10 Jul 2021 19:26:48 +
 Build duration:
31 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 7 test(s)Failed: projectroot.autotests.kiconloader_rcctest

KDE CI: Frameworks » kdelibs4support » kf5-qt5 WindowsMSVCQt5.15 - Build # 74 - Failure!

2021-07-10 Thread CI System
BUILD FAILURE
 Build URL
https://build.kde.org/job/Frameworks/job/kdelibs4support/job/kf5-qt5%20WindowsMSVCQt5.15/74/
 Project:
kf5-qt5 WindowsMSVCQt5.15
 Date of build:
Sat, 10 Jul 2021 19:24:39 +
 Build duration:
12 min and counting
   CONSOLE OUTPUT
  [...truncated 938 lines...][2021-07-10T19:36:38.571Z] ..\src\kdecore\kglobal.cpp: note: see previous definition of 'Q_OS_WIN'[2021-07-10T19:36:39.159Z] [153/533] Building CXX object src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\kbuttongroup.cpp.obj[2021-07-10T19:36:39.159Z] C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): warning C4005: 'Q_OS_WIN': macro redefinition[2021-07-10T19:36:39.159Z] ..\src\kdeui\kbuttongroup.cpp: note: see previous definition of 'Q_OS_WIN'[2021-07-10T19:36:39.159Z] [154/533] Building CXX object src\CMakeFiles\KF5KDELibs4Support.dir\kdecore\kascii.cpp.obj[2021-07-10T19:36:39.159Z] [155/533] Building CXX object src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\kaction.cpp.obj[2021-07-10T19:36:39.159Z] C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): warning C4005: 'Q_OS_WIN': macro redefinition[2021-07-10T19:36:39.159Z] ..\src\kdeui\kaction.cpp: note: see previous definition of 'Q_OS_WIN'[2021-07-10T19:36:39.434Z] [156/533] Building CXX object src\CMakeFiles\KF5KDELibs4Support.dir\kdecore\kurl.cpp.obj[2021-07-10T19:36:39.434Z] C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): warning C4005: 'Q_OS_WIN': macro redefinition[2021-07-10T19:36:39.434Z] ..\src\kdecore\kurl.cpp: note: see previous definition of 'Q_OS_WIN'[2021-07-10T19:36:39.434Z] KDE5 TODO: Remove tildeExpand feature for local paths[2021-07-10T19:36:39.434Z] [157/533] Building CXX object src\CMakeFiles\KF5KDELibs4Support.dir\kdecore\kcalendarsystemjalali.cpp.obj[2021-07-10T19:36:39.434Z] C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): warning C4005: 'Q_OS_WIN': macro redefinition[2021-07-10T19:36:39.434Z] ..\src\kdecore\kcalendarsystemjalali.cpp: note: see previous definition of 'Q_OS_WIN'[2021-07-10T19:36:39.434Z] [158/533] Building CXX object src\CMakeFiles\KF5KDELibs4Support.dir\kdecore\ktimezone.cpp.obj[2021-07-10T19:36:39.434Z] C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): warning C4005: 'Q_OS_WIN': macro redefinition[2021-07-10T19:36:39.434Z] ..\src\kdecore\ktimezone.cpp: note: see previous definition of 'Q_OS_WIN'[2021-07-10T19:36:39.705Z] [159/533] Building CXX object src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\k3icon.cpp.obj[2021-07-10T19:36:39.705Z] C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): warning C4005: 'Q_OS_WIN': macro redefinition[2021-07-10T19:36:39.705Z] ..\src\kdeui\k3icon.cpp: note: see previous definition of 'Q_OS_WIN'[2021-07-10T19:36:40.281Z] [160/533] Building CXX object src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\kcolordialog.cpp.obj[2021-07-10T19:36:40.281Z] C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): warning C4005: 'Q_OS_WIN': macro redefinition[2021-07-10T19:36:40.281Z] ..\src\kdeui\kcolordialog.cpp: note: see previous definition of 'Q_OS_WIN'[2021-07-10T19:36:40.281Z] [161/533] Building CXX object src\CMakeFiles\KF5KDELibs4Support.dir\kdecore\kcalendarsystemindiannational.cpp.obj[2021-07-10T19:36:40.281Z] C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): warning C4005: 'Q_OS_WIN': macro redefinition[2021-07-10T19:36:40.281Z] ..\src\kdecore\kcalendarsystemindiannational.cpp: note: see previous definition of 'Q_OS_WIN'[2021-07-10T19:36:40.281Z] [162/533] Building CXX object src\CMakeFiles\KF5KDELibs4Support.dir\kdecore\kcalendarsystemcoptic.cpp.obj[2021-07-10T19:36:40.281Z] C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): warning C4005: 'Q_OS_WIN': macro redefinition[2021-07-10T19:36:40.281Z] ..\src\kdecore\kcalendarsystemcoptic.cpp: note: see previous definition of 'Q_OS_WIN'[2021-07-10T19:36:40.281Z] [163/533] Building CXX object src\CMakeFiles\KF5KDELibs4Support.dir\kdecore\ksystemtimezone.cpp.obj[2021-07-10T19:36:40.281Z] C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): warning C4005: 'Q_OS_WIN': macro redefinition[2021-07-10T19:36:40.281Z] ..\src\kdecore\ksystemtimezone.cpp: note: see previous definition of 'Q_OS_WIN'[2021-07-10T19:36:40.859Z] [164/533] Building CXX object src\CMakeFiles\KF5KDELibs4Support.dir\kdecore\klocalizeddate.cpp.obj[2021-07-10T19:36:40.859Z] C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): warning C4005: 'Q_OS_WIN': macro redefinition[2021-07-10T19:36:40.859Z] ..\src\kdecore\klocalizeddate.cpp: note: see previous definition of 'Q_OS_WIN'[2021-07-10T19:36:41.126Z] [165/533] Building CXX object 

KDE CI: Frameworks » kio » kf5-qt5 SUSEQt5.15 - Build # 910 - Still Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.15/910/
 Project:
kf5-qt5 SUSEQt5.15
 Date of build:
Sat, 10 Jul 2021 18:10:36 +
 Build duration:
1 hr 0 min and counting
   BUILD ARTIFACTS
  acc/KF5KIO-5.84.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: 58 test(s), Skipped: 0 test(s), Total: 60 test(s)Failed: projectroot.autotests.kiocore_kprotocolinfotestFailed: projectroot.autotests.kiofilewidgets_kurlnavigatortestName: 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 Report68%
(25/37)68%
(291/425)68%
(291/425)58%
(38503/66835)41%
(21186/51115)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests94%
(59/63)94%
(59/63)90%
(10900/12164)45%
(6764/15177)autotests.http100%
(5/5)100%
(5/5)99%
(524/525)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%
(9402/15162)52%
(4661/8884)src.core.kssl100%
(1/1)100%
(1/1)39%
(34/87)50%
(3/6)src.filewidgets79%
(30/38)79%
(30/38)57%
(5174/9015)43%
(2197/5070)src.gui100%
(9/9)100%
(9/9)78%
(764/979)59%
(395/672)src.gui.systemd50%
(2/4)50%
(2/4)4%
(7/177)1%
(1/108)src.ioslaves.file100%
(7/7)100%
(7/7)57%
(792/1378)43%
(515/1190)src.ioslaves.file.kauth0%
(0/2)0%
(0/2)0%
(0/179)0%
(0/89)src.ioslaves.ftp100%
(2/2)100%
(2/2)49%
(672/1385)37%
(536/1434)src.ioslaves.help0%
(0/5)0%
(0/5)0%
(0/251)0%
(0/148)src.ioslaves.http88%
(7/8)88%
(7/8)43%
(1865/4341)37%
(1360/3719)src.ioslaves.http.kcookiejar40%
(2/5)40%
(2/5)49%
(661/1360)56%
(590/1055)src.ioslaves.remote100%

Re: Fwd: KDE CI: Administration » Dependency Build Applications stable-kf5-qt5 WindowsMSVCQt5.15 - Build # 52 - Still Failing!

2021-07-10 Thread Ben Cooksley
On Sat, Jul 10, 2021 at 9:14 PM Ralf Habacker 
wrote:

> Am 09.07.21 um 21:26 schrieb Ben Cooksley:
>
> Hi Ralf,
>
> I'm afraid your previous fixes are insufficient - we are still failing
> with a linking error.
>
> The following is notice that I intend to back all changes out in kdewin
> and restore the repository to 8503ac6e0e07099c4938cbfe60e3f5e25e2ec368 to
> restore the correct function of the CI system in 24 hours time.
>
> Please don't that not - that fix is required for building kdelibs4support
> with mingw headers version 9 and only export replacement functions not
> provided by the os.
>
The platform you are talking about (mingw cross compilation) is not one
generally supported by KDE on Windows - I believe you are the only person
who uses that approach.

The MingW version we do support (native compilation), along with MSVC (as
the principal compiler) do not have the issue you are describing.
This is how all the Binary Factory builds are run, and therefore how every
project on there is built.


> You should either revert the kdewin build script to checkout the source
> from a git tag (v0.6.4) and not master as done by other packages (I'm
> sorry, I cannot do that because of missing knowledge).
>
> At the  mentioned mingw cross build package for kdelib4support I need to
> add  -DHAVE_INET_PTON=1 -DHAVE_INET_NTOP=1 to the cmake configure as
> workaround to the broken inet_xxx function detection inside
> kdeblibs4support source.
>
Sorry, but that is not an option - the CI system builds the same set of
branches that a developer and our release managers build.
That means 'master'.

The fact that you have to apply additional overrides here indicates to me
that your changes to 'kdewin' are also incorrect.

Once the CI system has settled down following the Release Gear tagging i'll
be performing the revert as previously mentioned unless a fix to this is
pushed.


> Ralf
>
> Regards,
> Ben
>
>
Regards,
Ben


> -- Forwarded message -
> From: CI System 
> Date: Sat, Jul 10, 2021 at 7:21 AM
> Subject: KDE CI: Administration » Dependency Build Applications
> stable-kf5-qt5 WindowsMSVCQt5.15 - Build # 52 - Still Failing!
> To: 
>
>
> *BUILD FAILURE*
> Build URL
> https://build.kde.org/job/Administration/job/Dependency%20Build%20Applications%20stable-kf5-qt5%20WindowsMSVCQt5.15/52/
> Project: Dependency Build Applications stable-kf5-qt5 WindowsMSVCQt5.15
> Date of build: Fri, 09 Jul 2021 18:58:42 +
> Build duration: 22 min and counting
> * CONSOLE OUTPUT *
> [...truncated 51900 lines...]
> [2021-07-09T19:20:03.112Z]
> C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189):
> warning C4005: 'Q_OS_WIN': macro redefinition
> [2021-07-09T19:20:03.112Z] ..\src\kdeui\kicon.cpp: note: see previous
> definition of 'Q_OS_WIN'
> [2021-07-09T19:20:03.112Z] [153/533] Building CXX object
> src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\kdialogqueue.cpp.obj
> [2021-07-09T19:20:03.112Z]
> C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189):
> warning C4005: 'Q_OS_WIN': macro redefinition
> [2021-07-09T19:20:03.112Z] ..\src\kdeui\kdialogqueue.cpp: note: see
> previous definition of 'Q_OS_WIN'
> [2021-07-09T19:20:03.112Z] [154/533] Building CXX object
> src\CMakeFiles\KF5KDELibs4Support.dir\kdecore\ktzfiletimezone.cpp.obj
> [2021-07-09T19:20:03.112Z]
> C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189):
> warning C4005: 'Q_OS_WIN': macro redefinition
> [2021-07-09T19:20:03.112Z] ..\src\kdecore\ktzfiletimezone.cpp: note: see
> previous definition of 'Q_OS_WIN'
> [2021-07-09T19:20:03.112Z] [155/533] Building CXX object
> src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\kapplication.cpp.obj
> [2021-07-09T19:20:03.112Z]
> C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189):
> warning C4005: 'Q_OS_WIN': macro redefinition
> [2021-07-09T19:20:03.112Z] ..\src\kdeui\kapplication.cpp: note: see
> previous definition of 'Q_OS_WIN'
> [2021-07-09T19:20:03.684Z] [156/533] Building CXX object
> src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\kstringvalidator.cpp.obj
> [2021-07-09T19:20:03.684Z]
> C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189):
> warning C4005: 'Q_OS_WIN': macro redefinition
> [2021-07-09T19:20:03.684Z] ..\src\kdeui\kstringvalidator.cpp: note: see
> previous definition of 'Q_OS_WIN'
> [2021-07-09T19:20:03.684Z] [157/533] Building CXX object
> src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\kfadewidgeteffect.cpp.obj
> [2021-07-09T19:20:03.684Z]
> C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189):
> warning C4005: 'Q_OS_WIN': macro redefinition
> [2021-07-09T19:20:03.684Z] ..\src\kdeui\kfadewidgeteffect.cpp: note: see
> previous definition of 'Q_OS_WIN'
> [2021-07-09T19:20:03.945Z] [158/533] Building CXX object
> src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\kbuttongroup.cpp.obj
> 

KDE CI: Frameworks » kio » kf5-qt5 SUSEQt5.15 - Build # 909 - Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.15/909/
 Project:
kf5-qt5 SUSEQt5.15
 Date of build:
Sat, 10 Jul 2021 16:13:41 +
 Build duration:
1 hr 56 min and counting
   BUILD ARTIFACTS
  acc/KF5KIO-5.84.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: 58 test(s), Skipped: 0 test(s), Total: 60 test(s)Failed: projectroot.autotests.kiocore_kprotocolinfotestFailed: projectroot.autotests.kiofilewidgets_kurlnavigatortestName: 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 Report68%
(25/37)68%
(291/425)68%
(291/425)58%
(38499/66834)41%
(21194/51115)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests94%
(59/63)94%
(59/63)90%
(10900/12164)45%
(6774/15177)autotests.http100%
(5/5)100%
(5/5)99%
(524/525)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%
(9402/15162)52%
(4663/8884)src.core.kssl100%
(1/1)100%
(1/1)39%
(34/87)50%
(3/6)src.filewidgets79%
(30/38)79%
(30/38)57%
(5176/9015)43%
(2199/5070)src.gui100%
(9/9)100%
(9/9)78%
(764/979)59%
(395/672)src.gui.systemd50%
(2/4)50%
(2/4)4%
(7/177)1%
(1/108)src.ioslaves.file100%
(7/7)100%
(7/7)57%
(792/1378)43%
(515/1190)src.ioslaves.file.kauth0%
(0/2)0%
(0/2)0%
(0/179)0%
(0/89)src.ioslaves.ftp100%
(2/2)100%
(2/2)49%
(672/1385)37%
(536/1434)src.ioslaves.help0%
(0/5)0%
(0/5)0%
(0/251)0%
(0/148)src.ioslaves.http88%
(7/8)88%
(7/8)43%
(1864/4341)37%
(1358/3719)src.ioslaves.http.kcookiejar40%
(2/5)40%
(2/5)49%
(661/1360)56%
(590/1055)src.ioslaves.remote100%
   

Re: Porting notes / deprecation docs

2021-07-10 Thread Friedrich W. H. Kossebau
Am Samstag, 10. Juli 2021, 18:00:13 CEST schrieb Frederik Schwarzer:
> as mentioned earlier

Any pointers? :)

> I would like to document classes/methods/etc that
> are going to be deprecated during KF6 development.

Can you help confused-on-first-read people by explaining what "deprecated 
during KF6 development" is referring to? Deprecated during KF5 development and 
no longer be available in KF6? Not yet deprecated due to no existing 
replacement, but with replacement planned in KF6?

> For that I scraped up all the deprecation macros from the frameworks and
> edited them to be more unified.

That sounds like duplication of data, and worse, a manual copy of a certain 
state, which also needs to be manually maintained to be up-to-date to stay 
useful.

In general I am also curious what audience is targeted by the planned 
documentation and in which work-flows that documentation should solve which 
needs, and what other solutions are there which would not satisfy those needs 
well enough?

In general, for API already deprecated now during lifetime of KF5 we are 
adding porting notes to the very API itself. Which is also the place as API 
consumer I would be hoping for to get all needed information straight in one 
go, instead of having to jump to other places, which might even get out of 
sync or focus of developers (remember that current online docs of api.kde.org 
also only provide docs for latest version (and even the development one, not 
just the latest released).

And this is a change to what happened in kdelibs4 times, where most 
deprecation happened in the development branches for what became KDE 
Frameworks, so there also was no API documentation maintained at the same 
time. So copying the approach taken for the KDE Frameworks porting notes would 
not be needed here 1:1 for what I understand.

Instead we would need to add documentation for those things which are again 
deprecated (well, removed rather) during preparation of KF6, where the 
replacement also only will be in KF6, so no-one can port before.

Cheers
Friedrich




Re: Porting notes / deprecation docs

2021-07-10 Thread Frederik Schwarzer




On 7/10/21 6:17 PM, Ahmad Samir wrote:

On 10/07/2021 18:00, Frederik Schwarzer wrote:

Hi,

as mentioned earlier, I would like to document classes/methods/etc that
are going to be deprecated during KF6 development.

For that I scraped up all the deprecation macros from the frameworks and
edited them to be more unified.



Good work, that must have been a huge task! (82 frameworks ... :)).


grep ran a few seconds to give me a 2600 lines text file, which I then 
had to edit to be more readable, which took me several hours. :)

The hard part is still about to come. :)



As for the location, I would probably start putting content in the
community wiki to a place like
https://community.kde.org/Frameworks/KF6_Porting_Notes. Does anyone see
a problem with that? Might is be better to write such docs in markdown
or restructured text for being better suited for a more modern location?



A wiki page is not most friendly way of editing huge technical 
documents. Personally, I think a markdown file in a git repo would be 
great, and then it can be "published" to a wiki page or a static web 
page on one of KDE's web sites. Or, we start with an markdown text file, 
then after it's fleshed out / polished, put it in the wiki, 
editing/adding a small section here or there would be easier. (But I do 
prefer text files, much easier to edit in my usual editor of choice).


Yes, I agree. A text file in Git is also better for tracking changes.


FWIW, there is supposed to be a KF6 meeting soon[1]. Not sure if we'll 
start this week or the next one though.


I have the Mondays on my calendar now. :)



KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 913 - Still Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/913/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sat, 10 Jul 2021 17:16:13 +
 Build duration:
3 min 21 sec and counting
   JUnit Tests
  Name: projectroot Failed: 2 test(s), Passed: 57 test(s), Skipped: 0 test(s), Total: 59 test(s)Failed: projectroot.autotests.kiocore_kprotocolinfotestFailed: projectroot.autotests.kiofilewidgets_kurlnavigatortestName: 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)

Raising required Qt version to 5.15.2

2021-07-10 Thread Christoph Cullmann

Hi,

at the moment we require Qt 5.15.0 in Frameworks.

.2 introduced some new API functions for e.g. QStringView and
some merge requests are blocked due to that:

https://invent.kde.org/pim/kpimtextedit/-/merge_requests/11

Would it make sense to raise the bar to 5.15.2 for Frameworks?

Beside this, Qt 5.15.0 + .1 have a that broken QJSEngine that
even the trivial KTextEditor JS unit tests random fail
with GC crashs, I think it would make sense to really require
at least some "working" version.

Greetings
Christoph

--
Ignorance is bliss...
https://cullmann.io | https://kate-editor.org


KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 912 - Still Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/912/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sat, 10 Jul 2021 17:06:56 +
 Build duration:
9 min 14 sec and counting
   JUnit Tests
  Name: projectroot Failed: 3 test(s), Passed: 56 test(s), Skipped: 0 test(s), Total: 59 test(s)Failed: projectroot.autotests.commandlauncherjob_forkingtestFailed: projectroot.autotests.kiocore_kprotocolinfotestFailed: projectroot.autotests.kiofilewidgets_kurlnavigatortestName: 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 # 911 - Still Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/911/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sat, 10 Jul 2021 16:18:17 +
 Build duration:
4 min 49 sec and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 58 test(s), Skipped: 0 test(s), Total: 59 test(s)Failed: projectroot.autotests.kiofilewidgets_kurlnavigatortestName: 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 # 910 - Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/910/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sat, 10 Jul 2021 16:13:41 +
 Build duration:
4 min 33 sec and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 58 test(s), Skipped: 0 test(s), Total: 59 test(s)Failed: projectroot.autotests.kiofilewidgets_kurlnavigatortestName: 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)

Re: Porting notes / deprecation docs

2021-07-10 Thread Ahmad Samir

On 10/07/2021 18:00, Frederik Schwarzer wrote:

Hi,

as mentioned earlier, I would like to document classes/methods/etc that
are going to be deprecated during KF6 development.

For that I scraped up all the deprecation macros from the frameworks and
edited them to be more unified.



Good work, that must have been a huge task! (82 frameworks ... :)).


Now I need some opinions.

For once, there is still some stuff in deprecation from KDE4 times.
E.g. void setDoScanFile(bool scanFile); from kiowidgets.

I looked up a few of them in
https://community.kde.org/Frameworks/Porting_Notes but they are not
mentioned there.

Do you think these need to be mentioned in current porting notes as well
or have they been deprecated for long enough to consider them "over with"?



I would agree, these ones were probably just forgotten after the kdelibs split, and then couldn't be 
removed after the first KF5 release so as not to break BIC... etc. (Others who have been around 
longer will know for sure).




As for the location, I would probably start putting content in the
community wiki to a place like
https://community.kde.org/Frameworks/KF6_Porting_Notes. Does anyone see
a problem with that? Might is be better to write such docs in markdown
or restructured text for being better suited for a more modern location?



A wiki page is not most friendly way of editing huge technical documents. Personally, I think a 
markdown file in a git repo would be great, and then it can be "published" to a wiki page or a 
static web page on one of KDE's web sites. Or, we start with an markdown text file, then after it's 
fleshed out / polished, put it in the wiki, editing/adding a small section here or there would be 
easier. (But I do prefer text files, much easier to edit in my usual editor of choice).


FWIW, there is supposed to be a KF6 meeting soon[1]. Not sure if we'll start this week or the next 
one though.


[1] https://mail.kde.org/pipermail/kde-frameworks-devel/2021-July/118028.html



Thanks!

Cheers,
Frederik




--
Ahmad Samir


Porting notes / deprecation docs

2021-07-10 Thread Frederik Schwarzer

Hi,

as mentioned earlier, I would like to document classes/methods/etc that 
are going to be deprecated during KF6 development.


For that I scraped up all the deprecation macros from the frameworks and 
edited them to be more unified.


Now I need some opinions.

For once, there is still some stuff in deprecation from KDE4 times.
E.g. void setDoScanFile(bool scanFile); from kiowidgets.

I looked up a few of them in 
https://community.kde.org/Frameworks/Porting_Notes but they are not 
mentioned there.


Do you think these need to be mentioned in current porting notes as well 
or have they been deprecated for long enough to consider them "over with"?



As for the location, I would probably start putting content in the 
community wiki to a place like 
https://community.kde.org/Frameworks/KF6_Porting_Notes. Does anyone see 
a problem with that? Might is be better to write such docs in markdown 
or restructured text for being better suited for a more modern location?



Thanks!

Cheers,
Frederik


KDE CI: Frameworks » plasma-framework » kf5-qt5 FreeBSDQt5.15 - Build # 528 - Fixed!

2021-07-10 Thread CI System
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/plasma-framework/job/kf5-qt5%20FreeBSDQt5.15/528/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sat, 10 Jul 2021 14:45:47 +
 Build duration:
5 min 1 sec and counting
   JUnit Tests
  Name: projectroot Failed: 0 test(s), Passed: 11 test(s), Skipped: 0 test(s), Total: 11 test(s)

KDE CI: Frameworks » kwindowsystem » kf5-qt5 SUSEQt5.15 - Build # 95 - Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kwindowsystem/job/kf5-qt5%20SUSEQt5.15/95/
 Project:
kf5-qt5 SUSEQt5.15
 Date of build:
Sat, 10 Jul 2021 11:26:34 +
 Build duration:
31 min and counting
   BUILD ARTIFACTS
  acc/KF5WindowSystem-5.84.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: 12 test(s), Skipped: 0 test(s), Total: 13 test(s)Failed: projectroot.autotests.kwindowsystem_kwindowinfox11test
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report67%
(4/6)78%
(43/55)78%
(43/55)74%
(7530/10162)54%
(3935/7307)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests88%
(15/17)88%
(15/17)97%
(3162/3244)52%
(1631/3142)autotests.helper100%
(1/1)100%
(1/1)73%
(8/11)50%
(3/6)src85%
(11/13)85%
(11/13)55%
(905/1652)41%
(318/768)src.platforms.wayland0%
(0/2)0%
(0/2)0%
(0/70)100%
(0/0)src.platforms.xcb94%
(16/17)94%
(16/17)70%
(3455/4914)59%
(1983/3343)tests0%
(0/5)0%
(0/5)0%
(0/271)0%
(0/48)

KDE CI: Frameworks » kdav » kf5-qt5 SUSEQt5.15 - Build # 69 - Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kdav/job/kf5-qt5%20SUSEQt5.15/69/
 Project:
kf5-qt5 SUSEQt5.15
 Date of build:
Sat, 10 Jul 2021 11:26:35 +
 Build duration:
27 min and counting
   BUILD ARTIFACTS
  acc/KF5DAV-5.84.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: 5 test(s), Skipped: 0 test(s), Total: 6 test(s)Failed: projectroot.autotests.kdav_davcollectionsmultifetchjobtest
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report75%
(3/4)67%
(33/49)67%
(33/49)45%
(1018/2254)25%
(397/1568)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests100%
(7/7)100%
(7/7)91%
(358/395)50%
(217/437)src.common63%
(24/38)63%
(24/38)39%
(574/1463)24%
(168/693)src.protocols67%
(2/3)67%
(2/3)28%
(86/302)21%
(12/58)test0%
(0/1)0%
(0/1)0%
(0/94)0%
(0/380)

KDE CI: Frameworks » extra-cmake-modules » kf5-qt5 SUSEQt5.15 - Build # 236 - Still Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20SUSEQt5.15/236/
 Project:
kf5-qt5 SUSEQt5.15
 Date of build:
Sat, 10 Jul 2021 11:26:36 +
 Build duration:
16 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 19 test(s), Skipped: 0 test(s), Total: 20 test(s)Failed: projectroot.tests.ExecuteKDEModulesName: 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: 74 test(s), Skipped: 0 test(s), Total: 74 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 » kio » kf5-qt5 FreeBSDQt5.15 - Build # 909 - Fixed!

2021-07-10 Thread CI System
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/909/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sat, 10 Jul 2021 10:41:02 +
 Build duration:
26 min and counting
   JUnit Tests
  Name: projectroot Failed: 0 test(s), Passed: 59 test(s), Skipped: 0 test(s), Total: 59 test(s)Name: 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)

Re: Weekly KF6 meeting poll

2021-07-10 Thread Ahmad Samir

On 09/07/2021 19:08, Ahmad Samir wrote:

On 29/06/2021 16:48, Ahmad Samir wrote:

Hello, as was discussed during the KF6 BoF at Akademy, David Edmundson (aka "David 
2", not to be
confused with "David 1" aka "4" or David 3, aka "the David who still has all 
the hair on his
head"... sorry, I digress :)).

David has created a poll as a way to find a more suitable time for the weekly 
KF6 meeting (that we
used to have on Saturdays 13:00 UTC), apparently the link might have gone too 
far under the radar in
the KF6 meeting notes that were posted to this ML by Volker. So here it is, 
please vote:
https://doodle.com/poll/94646r75keyxgqkx

Have a good day.



It's been 18 days since the poll was created, I'd say that's long enough. If no 
one disagrees, I'd
say the deadline is today 00:00 UTC.

As it stands now, it looks like most of the participants find the 03:00 - 04:00 
PM slot most
convenient, and it's a tie between Monday, Tuesday and Friday (each with 
exactly 11 votes).

Best regards.



OK, poll is done now (since no one disagreed).

And the result is that it looks like we'll have the meeting on Mondays at 015:00-016:00 UTC. The 
BigBlueButton room link is at https://community.kde.org/Frameworks#Meetings (I'll update the wiki 
page with the new meeting time shortly).


Have a good day.

--
Ahmad Samir


KDE CI: Frameworks » kwayland » kf5-qt5 FreeBSDQt5.15 - Build # 95 - Still Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20FreeBSDQt5.15/95/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sat, 10 Jul 2021 10:41:02 +
 Build duration:
16 min and counting
   JUnit Tests
  Name: projectroot.autotests Failed: 12 test(s), Passed: 31 test(s), Skipped: 0 test(s), Total: 43 test(s)Failed: projectroot.autotests.client.kwayland_testCompositorFailed: projectroot.autotests.client.kwayland_testDataDeviceFailed: projectroot.autotests.client.kwayland_testDataSourceFailed: projectroot.autotests.client.kwayland_testRegionFailed: projectroot.autotests.client.kwayland_testShmPoolFailed: projectroot.autotests.client.kwayland_testSubCompositorFailed: projectroot.autotests.client.kwayland_testSubSurfaceFailed: projectroot.autotests.client.kwayland_testWaylandConnectionThreadFailed: projectroot.autotests.client.kwayland_testWaylandRegistryFailed: projectroot.autotests.client.kwayland_testWaylandShellFailed: projectroot.autotests.client.kwayland_testWaylandSurfaceFailed: projectroot.autotests.server.kwayland_testWaylandServerDisplay

KDE CI: Frameworks » extra-cmake-modules » kf5-qt5 FreeBSDQt5.15 - Build # 207 - Still Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20FreeBSDQt5.15/207/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sat, 10 Jul 2021 10:41:01 +
 Build duration:
4 min 11 sec and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 19 test(s), Skipped: 0 test(s), Total: 20 test(s)Failed: projectroot.tests.ExecuteKDEModulesName: projectroot.tests Failed: 0 test(s), Passed: 64 test(s), Skipped: 0 test(s), Total: 64 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 # 206 - Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20FreeBSDQt5.15/206/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sat, 10 Jul 2021 10:10:49 +
 Build duration:
5 min 31 sec and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 19 test(s), Skipped: 0 test(s), Total: 20 test(s)Failed: projectroot.tests.ExecuteKDEModulesName: projectroot.tests Failed: 0 test(s), Passed: 64 test(s), Skipped: 0 test(s), Total: 64 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 SUSEQt5.15 - Build # 235 - Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20SUSEQt5.15/235/
 Project:
kf5-qt5 SUSEQt5.15
 Date of build:
Sat, 10 Jul 2021 10:10:49 +
 Build duration:
4 min 14 sec and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 19 test(s), Skipped: 0 test(s), Total: 20 test(s)Failed: projectroot.tests.ExecuteKDEModulesName: 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: 74 test(s), Skipped: 0 test(s), Total: 74 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 # 233 - Fixed!

2021-07-10 Thread CI System
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20SUSEQt5.15/233/
 Project:
kf5-qt5 SUSEQt5.15
 Date of build:
Sat, 10 Jul 2021 09:46:29 +
 Build duration:
4 min 8 sec and counting
   JUnit Tests
  Name: projectroot Failed: 0 test(s), Passed: 20 test(s), Skipped: 0 test(s), Total: 20 test(s)Name: 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: 74 test(s), Skipped: 0 test(s), Total: 74 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 # 204 - Fixed!

2021-07-10 Thread CI System
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20FreeBSDQt5.15/204/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sat, 10 Jul 2021 09:46:29 +
 Build duration:
2 min 53 sec and counting
   JUnit Tests
  Name: projectroot Failed: 0 test(s), Passed: 20 test(s), Skipped: 0 test(s), Total: 20 test(s)Name: projectroot.tests Failed: 0 test(s), Passed: 64 test(s), Skipped: 0 test(s), Total: 64 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 SUSEQt5.15 - Build # 232 - Still Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20SUSEQt5.15/232/
 Project:
kf5-qt5 SUSEQt5.15
 Date of build:
Sat, 10 Jul 2021 09:42:02 +
 Build duration:
3 min 50 sec and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 19 test(s), Skipped: 0 test(s), Total: 20 test(s)Failed: projectroot.tests.ExecuteKDEModulesName: 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: 74 test(s), Skipped: 0 test(s), Total: 74 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 # 231 - Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20SUSEQt5.15/231/
 Project:
kf5-qt5 SUSEQt5.15
 Date of build:
Sat, 10 Jul 2021 09:38:29 +
 Build duration:
3 min 32 sec and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 19 test(s), Skipped: 0 test(s), Total: 20 test(s)Failed: projectroot.tests.ExecuteKDEModulesName: 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: 74 test(s), Skipped: 0 test(s), Total: 74 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 # 203 - Unstable!

2021-07-10 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20FreeBSDQt5.15/203/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sat, 10 Jul 2021 09:38:29 +
 Build duration:
3 min 28 sec and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 19 test(s), Skipped: 0 test(s), Total: 20 test(s)Failed: projectroot.tests.ExecuteKDEModulesName: projectroot.tests Failed: 0 test(s), Passed: 64 test(s), Skipped: 0 test(s), Total: 64 test(s)Name: projectroot.tests.ECMAddTests Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)

Re: Fwd: KDE CI: Administration » Dependency Build Applications stable-kf5-qt5 WindowsMSVCQt5.15 - Build # 52 - Still Failing!

2021-07-10 Thread Ralf Habacker

Am 09.07.21 um 21:26 schrieb Ben Cooksley:

Hi Ralf,

I'm afraid your previous fixes are insufficient - we are still failing 
with a linking error.


The following is notice that I intend to back all changes out in 
kdewin and restore the repository to 
8503ac6e0e07099c4938cbfe60e3f5e25e2ec368 to restore the correct 
function of the CI system in 24 hours time.


Please don't that not - that fix is required for building 
kdelibs4support with mingw headers version 9 and only export replacement 
functions not provided by the os.


You should either revert the kdewin build script to checkout the source 
from a git tag (v0.6.4) and not master as done by other packages (I'm 
sorry, I cannot do that because of missing knowledge).


At the  mentioned mingw cross build package for kdelib4support I need to 
add  -DHAVE_INET_PTON=1 -DHAVE_INET_NTOP=1 to the cmake configure as 
workaround to the broken inet_xxx function detection inside 
kdeblibs4support source.


Ralf


Regards,
Ben

-- Forwarded message -
From: *CI System* mailto:nore...@kde.org>>
Date: Sat, Jul 10, 2021 at 7:21 AM
Subject: KDE CI: Administration » Dependency Build Applications 
stable-kf5-qt5 WindowsMSVCQt5.15 - Build # 52 - Still Failing!

To: mailto:bcooks...@kde.org>>


*BUILD FAILURE*
Build URL 
https://build.kde.org/job/Administration/job/Dependency%20Build%20Applications%20stable-kf5-qt5%20WindowsMSVCQt5.15/52/ 
 


Project:Dependency Build Applications stable-kf5-qt5 WindowsMSVCQt5.15
Date of build:  Fri, 09 Jul 2021 18:58:42 +
Build duration: 22 min and counting


*CONSOLE OUTPUT *
[...truncated 51900 lines...]
[2021-07-09T19:20:03.112Z] 
C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): 
warning C4005: 'Q_OS_WIN': macro redefinition
[2021-07-09T19:20:03.112Z] ..\src\kdeui\kicon.cpp: note: see previous 
definition of 'Q_OS_WIN'
[2021-07-09T19:20:03.112Z] [153/533] Building CXX object 
src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\kdialogqueue.cpp.obj
[2021-07-09T19:20:03.112Z] 
C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): 
warning C4005: 'Q_OS_WIN': macro redefinition
[2021-07-09T19:20:03.112Z] ..\src\kdeui\kdialogqueue.cpp: note: see 
previous definition of 'Q_OS_WIN'
[2021-07-09T19:20:03.112Z] [154/533] Building CXX object 
src\CMakeFiles\KF5KDELibs4Support.dir\kdecore\ktzfiletimezone.cpp.obj
[2021-07-09T19:20:03.112Z] 
C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): 
warning C4005: 'Q_OS_WIN': macro redefinition
[2021-07-09T19:20:03.112Z] ..\src\kdecore\ktzfiletimezone.cpp: note: 
see previous definition of 'Q_OS_WIN'
[2021-07-09T19:20:03.112Z] [155/533] Building CXX object 
src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\kapplication.cpp.obj
[2021-07-09T19:20:03.112Z] 
C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): 
warning C4005: 'Q_OS_WIN': macro redefinition
[2021-07-09T19:20:03.112Z] ..\src\kdeui\kapplication.cpp: note: see 
previous definition of 'Q_OS_WIN'
[2021-07-09T19:20:03.684Z] [156/533] Building CXX object 
src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\kstringvalidator.cpp.obj
[2021-07-09T19:20:03.684Z] 
C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): 
warning C4005: 'Q_OS_WIN': macro redefinition
[2021-07-09T19:20:03.684Z] ..\src\kdeui\kstringvalidator.cpp: note: 
see previous definition of 'Q_OS_WIN'
[2021-07-09T19:20:03.684Z] [157/533] Building CXX object 
src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\kfadewidgeteffect.cpp.obj
[2021-07-09T19:20:03.684Z] 
C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): 
warning C4005: 'Q_OS_WIN': macro redefinition
[2021-07-09T19:20:03.684Z] ..\src\kdeui\kfadewidgeteffect.cpp: note: 
see previous definition of 'Q_OS_WIN'
[2021-07-09T19:20:03.945Z] [158/533] Building CXX object 
src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\kbuttongroup.cpp.obj
[2021-07-09T19:20:03.945Z] 
C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): 
warning C4005: 'Q_OS_WIN': macro redefinition
[2021-07-09T19:20:03.945Z] ..\src\kdeui\kbuttongroup.cpp: note: see 
previous definition of 'Q_OS_WIN'
[2021-07-09T19:20:04.205Z] [159/533] Building CXX object 
src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\kaction.cpp.obj
[2021-07-09T19:20:04.205Z] 
C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\include\qt5\QtCore/qsystemdetection.h(189): 
warning C4005: 'Q_OS_WIN': macro redefinition
[2021-07-09T19:20:04.205Z] ..\src\kdeui\kaction.cpp: note: see 
previous definition of 'Q_OS_WIN'
[2021-07-09T19:20:04.205Z] [160/533] Building CXX object 
src\CMakeFiles\KF5KDELibs4Support.dir\kdeui\ksessionmanager.cpp.obj
[2021-07-09T19:20:04.205Z]