KDE CI: Frameworks » kwayland » kf5-qt5 FreeBSDQt5.15 - Build # 99 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20FreeBSDQt5.15/99/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Tue, 13 Jul 2021 22:32:39 + Build duration: 6 min 35 sec 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_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.client.kwayland_testXdgShellV6Failed: projectroot.autotests.server.kwayland_testWaylandServerDisplay
KDE CI: Frameworks » solid » kf5-qt5 WindowsMSVCQt5.15 - Build # 93 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/solid/job/kf5-qt5%20WindowsMSVCQt5.15/93/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Tue, 13 Jul 2021 19:29:01 + Build duration: 2 min 2 sec and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)
Re: Porting notes / deprecation docs
Am Dienstag, 13. Juli 2021, 18:46:35 CEST schrieb Frederik Schwarzer: > On 7/12/21 8:43 PM, Friedrich W. H. Kossebau wrote: > > IIRC main file of the generation is > > https://invent.kde.org/websites/quality-kde-org/-/blob/master/apidox/src/ > > gendox.sh > > > > But I dropped out when there were people talking about their progress in > > writing a replacement and put my hopes & bet on them. But seems life got > > in > > then it seems... > > I cannot check what is used on the server but I was told > https://invent.kde.org/frameworks/kapidox/-/blob/master/src/kapidox_generate > would be the script that generates apidocs on the server. quality-kde-org code still is the one being run, and it invokes kapidox_generate in the process Cheers Friedrich
Re: Porting notes / deprecation docs
On 7/12/21 8:43 PM, Friedrich W. H. Kossebau wrote: Am Montag, 12. Juli 2021, 20:22:30 CEST schrieb Frederik Schwarzer: On 7/12/21 7:38 PM, Friedrich W. H. Kossebau wrote: Now what is meant by "clickable links to replacements" exactly? Any example for what you have in mind? (Just in case, Doxygen usually itself already generated automatic links to the functions (just needs complete signature, incl. const), see also https://www.doxygen.nl/manual/autolink.html but then I would guess you know that) Yes, that's what I meant. api.k.o does have clickable links (if done properly) but compiler warnings do not. That's why it would be good to keep the KF5 api docs. Ah, so html pages on a server/local docs in QCH vs. compiler log, I see :) If we put URLs in the messages, we could click them in Konsole. ;) Any insight on how you kept the KDE 2-4 apidocs alive? Mainly defending against admin wanting to clean up dead stuff and just wiping the current freak setup behind api.kde.org ;) (which is https:// invent.kde.org/websites/quality-kde-org) Right now the kdelibs 2-4 docs are no longer regenerated (at the time when I got involved only the 4 one still was, but now also no longer is, and just is static files on the web server. I did some URL updates e.g. for trolltech.com- qt.io using mass regexp replacements on them). IIRC main file of the generation is https://invent.kde.org/websites/quality-kde-org/-/blob/master/apidox/src/ gendox.sh But I dropped out when there were people talking about their progress in writing a replacement and put my hopes & bet on them. But seems life got in then it seems... I cannot check what is used on the server but I was told https://invent.kde.org/frameworks/kapidox/-/blob/master/src/kapidox_generate would be the script that generates apidocs on the server. Maybe someone can clarify? CHeers, Frederik
