KDE CI: Frameworks » baloo » kf5-qt5 SUSEQt5.15 - Build # 218 - Successful!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/baloo/job/kf5-qt5%20SUSEQt5.15/218/ Project: kf5-qt5 SUSEQt5.15 Date of build: Sun, 06 Feb 2022 08:16:58 + Build duration: 2 min 56 sec and counting BUILD ARTIFACTS acc/KF5Baloo-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.autotests Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: projectroot.autotests.unit Failed: 0 test(s), Passed: 34 test(s), Skipped: 0 test(s), Total: 34 test(s) Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report42% (10/24)60% (102/171)60% (102/171)61% (6953/11321)44% (3367/7573)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests.benchmarks0% (0/2)0% (0/2)0% (0/50)0% (0/22)autotests.integration100% (3/3)100% (3/3)94% (566/600)68% (329/486)autotests.unit.codecs100% (3/3)100% (3/3)100% (78/78)58% (38/66)autotests.unit.engine100% (18/18)100% (18/18)100% (979/979)56% (530/952)autotests.unit.file92% (12/13)92% (12/13)98% (1488/1514)53% (781/1476)autotests.unit.lib100% (4/4)100% (4/4)99% (418/419)55% (163/298)src.codecs100% (5/5)100% (5/5)90% (139/155)76% (38/50)src.engine90% (36/40)90% (36/40)77% (1872/2443)55% (779/1412)src.file40% (14/35)40% (14/35)50% (950/1899)42% (469/1128)src.file.extractor20% (1/5)20% (1/5)24% (57/236)16% (19/116)src.kioslaves.common0% (0/2)0% (0/2)0% (0/45)0% (0/14)src.kioslaves.kded0% (0/1)0% (0/1)0% (0/35)0% (0/30)src.kioslaves.search0% (0/1)0% (0/1)0% (0/49)0% (0/6)src.kioslaves.tags0% (0/1)0% (0/1)0% (0/271)0% (0/219)src.kioslaves.timeline0% (0/2)0% (0/2)0% (0/232)0% (0/131)src.lib50% (6/12)50% (6/12)41% (406/981)37% (221/593)src.qml0% (0/2)0% (0/2)0% (0/69)0%
KF 5.91: 24 modules with failing unit tests (Re: Please fix failing unit tests with Windows platform)
Am Montag, 24. Januar 2022, 01:06:40 CET schrieb Friedrich W. H. Kossebau: > Hi, > > since a long time there are lots of failing unit tests across multiple > repositories. Could the Windows platform maintainers/stakeholders please > look soonish into either fixing those tests or properly marking them as > expected to fail, so the resources the KDE CI spends on running the tests > every hour, day and week make some sense again, as well as having something > usable to diff results again, to notice any new regressions? > > Please see > > https://build.kde.org/job/Frameworks/view/Platform%20-%20WindowsMSVCQt5.15/ > (best sort by "S" build status to get a list what need And those who believe in the broken windows theory also would claim this slacking now resulted in the regressions in the openSUSE builds, where 5 modules now have failing unit tests at time of release tagging, when it once was 0 thanks to hard work of David F. and others. :( Is it time to remove https://community.kde.org/Frameworks/ Policies#Frameworks_CI_failures_are_treated_as_stop_the_line_events because seemingly this is just old dead pixels on a web page and not the spirit these days? Friedrich
KDE CI: Frameworks » kwayland » kf5-qt5 SUSEQt5.15 - Build # 165 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20SUSEQt5.15/165/ Project: kf5-qt5 SUSEQt5.15 Date of build: Sun, 06 Feb 2022 09:44:24 + Build duration: 6 min 20 sec and counting BUILD ARTIFACTS acc/KF5Wayland-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.autotests Failed: 0 test(s), Passed: 47 test(s), Skipped: 0 test(s), Total: 47 test(s) Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report63% (5/8)90% (218/241)90% (218/241)84% (28397/33662)53% (12808/24365)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests.client100% (43/43)100% (43/43)99% (13108/13179)50% (8215/16335)autotests.server100% (6/6)100% (6/6)99% (539/542)50% (283/568)src.client97% (72/74)97% (72/74)83% (6381/7675)64% (1834/2886)src.compat100% (2/2)100% (2/2)100% (78/78)100% (0/0)src.server96% (95/99)96% (95/99)83% (8291/9964)63% (2476/3933)src.tools0% (0/2)0% (0/2)0% (0/795)0% (0/308)src.tools.testserver0% (0/2)0% (0/2)0% (0/124)0% (0/16)tests0% (0/13)0% (0/13)0% (0/1305)0% (0/319)
KDE CI: Frameworks » kwayland » kf5-qt5 FreeBSDQt5.15 - Build # 151 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20FreeBSDQt5.15/151/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sun, 06 Feb 2022 09:44:24 + Build duration: 8 min 53 sec and counting JUnit Tests Name: projectroot.autotests Failed: 13 test(s), Passed: 33 test(s), Skipped: 0 test(s), Total: 46 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_testWaylandSeatFailed: projectroot.autotests.client.kwayland_testWaylandShellFailed: projectroot.autotests.client.kwayland_testWaylandSurfaceFailed: projectroot.autotests.server.kwayland_testWaylandServerDisplay
KDE CI: Frameworks » kwayland » kf5-qt5 FreeBSDQt5.15 - Build # 152 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20FreeBSDQt5.15/152/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sun, 06 Feb 2022 09:53:19 + Build duration: 8 min 8 sec and counting JUnit Tests Name: projectroot.autotests Failed: 14 test(s), Passed: 32 test(s), Skipped: 0 test(s), Total: 46 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_testWaylandSeatFailed: projectroot.autotests.client.kwayland_testWaylandShellFailed: projectroot.autotests.client.kwayland_testWaylandSurfaceFailed: projectroot.autotests.client.kwayland_testXdgShellV6Failed: projectroot.autotests.server.kwayland_testWaylandServerDisplay
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1376 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1376/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sun, 06 Feb 2022 09:54:44 + Build duration: 10 min 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 FreeBSDQt5.15 - Build # 1377 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1377/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sun, 06 Feb 2022 10:05:16 + Build duration: 4 min 35 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 FreeBSDQt5.15 - Build # 1378 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1378/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sun, 06 Feb 2022 14:40:31 + Build duration: 9 min 55 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.kiocore_ktcpsockettestFailed: projectroot.autotests.kiogui_openurljobtestFailed: 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 FreeBSDQt5.15 - Build # 1379 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1379/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sun, 06 Feb 2022 14:50:29 + Build duration: 8 min 53 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_servicetestFailed: 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)
Re: Critical Denial of Service bugs in Discover
On Sun, Feb 6, 2022 at 1:07 PM Fabian Vogt wrote: > Hi, > > Am Samstag, 5. Februar 2022, 22:16:28 CET schrieb Ben Cooksley: > > Hi all, > > > > Over the past week or so Sysadmin has been dealing with an extremely high > > volume of traffic directed towards both download.kde.org and > > distribute.kde.org. > > > > This traffic volume is curious in so far that it is directed at two paths > > specifically: > > - distribute.kde.org/khotnewstuff/fonts-providers.xml > > - download.kde.org/ocs/providers.xml > > > > The first path is an "internal only" host which we were redirecting a > > legacy path to prior to the resource being relocated to cdn.kde.org. The > > second path has been legacy for numerous years now (more than 5) and is > > replaced by autoconfig.kde.org. > > It is of extreme concern that these paths are still in use - especially > the > > ocs/providers.xml one. > > > >... > > > > This indicates that the bug lies solely within Plasma's Discover > component > > - more precisely it's updater. > > > > Examining the origin of these requests has indicated that some clients > are > > making requests to these paths well in excess of several times a minute > > with a number of IP addresses appearing more 60 times in a 1 minute sized > > sample window. > > FWICT, this is caused by plasma-discover-update, which is triggered by the > DiscoverNotifier service if automatic updates are enabled in kcm_updates, > updates are available and the system idle for >=15min. > > // If the system is untouched for 1 hour, trigger the unattened update > using namespace std::chrono_literals; > > KIdleTime::instance()->addIdleTimeout(int(std::chrono::milliseconds(15min).count())); > > (I wonder whether there's a bug about calling addIdleTimeout more than > once. > It will then invoke triggerUpdate multiple times after 15min of idle.) > That may explain why we are seeing so many requests from some IPs and very few from others. > > The Discover KNS backend creates instances for all available knsrc files, > which on construction call KNSReviews::setProviderUrl with the URL defined > in > those files, triggering the requests. > That does not sound scalable, and would certainly explain why not too long ago we found that the traffic received by autoconfig.kde.org had grown to such an extent we had to shift it to being handled by a CDN. At the time I chalked the problem up to increasing popularity of our software that included KNS functionality. > > 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. > > > Given that Sysadmin has raised issues with this component and it's > > behaviour in the past, it appears that issues regarding the behaviour of > > the OCS componentry within Discover remain unresolved. > > > > Due to the level of distress this is causing our systems, I am therefore > > left with no other option other than to direct the Plasma Discover > > developers to create and release without delay patches for all versions > in > > support, as well as for all those currently present in any actively > > maintained distributions, that disable all OCS functionality in the > > Discover updater. Distributions are requested to treat these patches as > > security patches and to distribute them to users without delay. > > Emergency workarounds for distributions might be to either not ship the KNS > backend by not building kns-backend.so or deleting it afterwards, or > disabling > the discover notifier > (/etc/xdg/autostart/org.kde.discover.notifier.desktop) > completely. > I have now committed patches to Discover going back to Plasma/5.18 which disable the build of the KNS backend. If distributions could please pick them up and distribute them as I previously indicated that would be much appreciated. https://invent.kde.org/plasma/discover/-/commit/f66df3531670592960167f5060feeed6d6c792be Please note that I intend to investigate whether it is possible to serve corrupted files from the server side that cause Discover to crash
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1380 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1380/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sun, 06 Feb 2022 19:11:17 + Build duration: 4 min 54 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 FreeBSDQt5.15 - Build # 1381 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1381/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sun, 06 Feb 2022 19:16:15 + Build duration: 5 min 22 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)
Re: KF 5.91: 24 modules with failing unit tests (Re: Please fix failing unit tests with Windows platform)
El diumenge, 6 de febrer de 2022, a les 10:40:22 (CET), Friedrich W. H. Kossebau va escriure: > Am Montag, 24. Januar 2022, 01:06:40 CET schrieb Friedrich W. H. Kossebau: > > Hi, > > > > since a long time there are lots of failing unit tests across multiple > > repositories. Could the Windows platform maintainers/stakeholders please > > look soonish into either fixing those tests or properly marking them as > > expected to fail, so the resources the KDE CI spends on running the tests > > every hour, day and week make some sense again, as well as having something > > usable to diff results again, to notice any new regressions? > > > > Please see > > > > https://build.kde.org/job/Frameworks/view/Platform%20-%20WindowsMSVCQt5.15/ > > (best sort by "S" build status to get a list what need > > And those who believe in the broken windows theory also would claim this > slacking now resulted in the regressions in the openSUSE builds, where 5 > modules now have failing unit tests at time of release tagging, when it once > was 0 thanks to hard work of David F. and others. :( Are you really saying "Since no one cares to fix the failing Windows tests, no one cares to fix failing openSUSE tests either"? Or did I misunderstood you here? Albert > > Is it time to remove > https://community.kde.org/Frameworks/ > Policies#Frameworks_CI_failures_are_treated_as_stop_the_line_events > because seemingly this is just old dead pixels on a web page and not the > spirit these days? > > Friedrich > > > >
Re: Critical Denial of Service bugs in Discover
Hi, Am Samstag, 5. Februar 2022, 22:16:28 CET schrieb Ben Cooksley: > Hi all, > > Over the past week or so Sysadmin has been dealing with an extremely high > volume of traffic directed towards both download.kde.org and > distribute.kde.org. > > This traffic volume is curious in so far that it is directed at two paths > specifically: > - distribute.kde.org/khotnewstuff/fonts-providers.xml > - download.kde.org/ocs/providers.xml > > The first path is an "internal only" host which we were redirecting a > legacy path to prior to the resource being relocated to cdn.kde.org. The > second path has been legacy for numerous years now (more than 5) and is > replaced by autoconfig.kde.org. > It is of extreme concern that these paths are still in use - especially the > ocs/providers.xml one. > >... > > This indicates that the bug lies solely within Plasma's Discover component > - more precisely it's updater. > > Examining the origin of these requests has indicated that some clients are > making requests to these paths well in excess of several times a minute > with a number of IP addresses appearing more 60 times in a 1 minute sized > sample window. FWICT, this is caused by plasma-discover-update, which is triggered by the DiscoverNotifier service if automatic updates are enabled in kcm_updates, updates are available and the system idle for >=15min. // If the system is untouched for 1 hour, trigger the unattened update using namespace std::chrono_literals; KIdleTime::instance()->addIdleTimeout(int(std::chrono::milliseconds(15min).count())); (I wonder whether there's a bug about calling addIdleTimeout more than once. It will then invoke triggerUpdate multiple times after 15min of idle.) The Discover KNS backend creates instances for all available knsrc files, which on construction call KNSReviews::setProviderUrl with the URL defined in those files, triggering the requests. 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 > Given that Sysadmin has raised issues with this component and it's > behaviour in the past, it appears that issues regarding the behaviour of > the OCS componentry within Discover remain unresolved. > > Due to the level of distress this is causing our systems, I am therefore > left with no other option other than to direct the Plasma Discover > developers to create and release without delay patches for all versions in > support, as well as for all those currently present in any actively > maintained distributions, that disable all OCS functionality in the > Discover updater. Distributions are requested to treat these patches as > security patches and to distribute them to users without delay. Emergency workarounds for distributions might be to either not ship the KNS backend by not building kns-backend.so or deleting it afterwards, or disabling the discover notifier (/etc/xdg/autostart/org.kde.discover.notifier.desktop) completely. Cheers, Fabian
Re: Critical Denial of Service bugs in Discover
Moin, 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. Does this decrease the server load noticably? On IRC you wrote that the primary offender is "KNewStuff/5.86.0-plasma-discover-update/", can you make the endpoints return an error for the top entries only? Then we'll get bug reports only for the likely cause(s) of the high traffic instead of everyone. What might help is to have a lightweight proxy in front of Apache to handle those paths in a way that doesn't stress the system much. That should probably be investigated independently of the client side, as this is entirely under our control and has immediate effects. 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. > > > Given that Sysadmin has raised issues with this component and it's > > > behaviour in the past, it appears that issues regarding the behaviour of > > > the OCS componentry within Discover remain unresolved. > > > > > > Due to the level of distress this is causing our systems, I am therefore > > > left with no other option other than to direct the Plasma Discover > > > developers to create and release without delay patches for all versions > > in > > > support, as well as for all those currently present in any actively > > > maintained distributions, that disable all OCS functionality in the > > > Discover updater. Distributions are requested to treat these patches as > > > security patches and to distribute them to users without delay. > > > > Emergency workarounds for distributions might be to either not ship the KNS > > backend by not building kns-backend.so or deleting it afterwards, or > > disabling > > the discover notifier > > (/etc/xdg/autostart/org.kde.discover.notifier.desktop) > > completely. > > I have now committed patches to Discover going back to Plasma/5.18 which > disable the build of the KNS backend. > If distributions could please pick them up and distribute them as I > previously indicated that would be much appreciated. > > https://invent.kde.org/plasma/discover/-/commit/f66df3531670592960167f5060feeed6d6c792be IMO we need a more targeted approach there. The main offenders aren't running the latest version, so likely won't get those updates that quickly either. If we have more data and can pinpoint it a bit better that would at least help to speed patch delivery up. > Please note that I intend to investigate whether it is possible to serve > corrupted files from the server side that cause Discover to crash to help > alleviate the load being created by those clients. Sounds like a good way to DoS bugzilla instead and cause bad PR, both up- and downstream. On top of that, it's possible that a resulting crashloop causes an even higher frequency of requests. Cheers, Fabian > Current load being generated by this is: > > 789 requests/sec - 6.4 MB/second - 8.3 kB/request - 1.70113 > ms/request > 217 requests currently being processed, 183 idle workers > > > Cheers, > > Fabian > > > Thanks, > Ben
KDE CI: Frameworks » kwidgetsaddons » kf5-qt5 FreeBSDQt5.15 - Build # 267 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kwidgetsaddons/job/kf5-qt5%20FreeBSDQt5.15/267/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sun, 06 Feb 2022 22:32:28 + Build duration: 1 min 27 sec and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 24 test(s), Skipped: 0 test(s), Total: 24 test(s)
KDE CI: Frameworks » kwidgetsaddons » kf5-qt5 SUSEQt5.15 - Build # 280 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kwidgetsaddons/job/kf5-qt5%20SUSEQt5.15/280/ Project: kf5-qt5 SUSEQt5.15 Date of build: Sun, 06 Feb 2022 22:32:28 + Build duration: 5 min 56 sec and counting BUILD ARTIFACTS acc/KF5WidgetsAddons-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: 24 test(s), Skipped: 0 test(s), Total: 24 test(s) Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report50% (2/4)44% (83/187)44% (83/187)38% (6567/17222)29% (2447/8431)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests100% (25/25)100% (25/25)99% (2446/2468)49% (1140/2304)examples.kmessagebox0% (0/1)0% (0/1)0% (0/15)0% (0/2)src47% (58/123)47% (58/123)31% (4121/13327)22% (1307/5922)tests0% (0/38)0% (0/38)0% (0/1412)0% (0/203)
KDE CI: Frameworks » kirigami » kf5-qt5 WindowsMSVCQt5.15 - Build # 660 - Failure!
BUILD FAILURE Build URL https://build.kde.org/job/Frameworks/job/kirigami/job/kf5-qt5%20WindowsMSVCQt5.15/660/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Sun, 06 Feb 2022 23:55:33 + Build duration: 19 sec and counting CONSOLE OUTPUT [...truncated 186 lines...][2022-02-06T23:55:44.841Z] __VSCMD_PREINIT_PATH = 'C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\Python38\Scripts\;C:\Program Files\Python38\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Git\cmd;C:\Users\Jenkins\AppData\Local\Microsoft\WindowsApps'[2022-02-06T23:55:44.841Z] __VSCMD_SCRIPT_ERR_COUNT = '0'[2022-02-06T23:55:44.841Z] CMAKE_PREFIX_PATH = 'C:\CI\Software Installs\kirigami;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\dev-utils'[2022-02-06T23:55:44.841Z] XDG_DATA_DIRS = 'C:\CI\Software Installs\kirigami\share;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\share;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\dev-utils\share'[2022-02-06T23:55:44.841Z] PKG_CONFIG_PATH = 'C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\lib\pkgconfig;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\dev-utils\lib\pkgconfig'[2022-02-06T23:55:44.841Z] QT_PLUGIN_PATH= 'C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\lib\qca-qt5;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\bin\plugins'[2022-02-06T23:55:44.841Z] QMAKEFEATURES = 'C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\mkspecs/features'[2022-02-06T23:55:44.841Z] QT_DATA_DIRS = 'C:\CI\Software Installs\kirigami\share;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\share;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\dev-utils\share'[2022-02-06T23:55:44.841Z] XDG_CURRENT_DESKTOP = 'KDE'[2022-02-06T23:55:44.841Z] ASAN_OPTIONS = 'detect_leaks=0:new_delete_type_mismatch=0:detect_odr_violation=0:stack-use-after-scope=0:alloc_dealloc_mismatch=0'[2022-02-06T23:55:44.841Z] [2022-02-06T23:55:44.841Z] [2022-02-06T23:55:44.841Z] == Commencing Configuration:[2022-02-06T23:55:44.841Z] cmake -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTING=ON -DCMAKE_INSTALL_PREFIX="C:/CI/Software Installs/kirigami/" -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -G "Ninja" -DBUILD_QCH=TRUE -DBUILD_EXAMPLES=ON "C:\CI\Job Build"[2022-02-06T23:55:45.793Z] -- The C compiler identification is MSVC 19.29.30038.1[2022-02-06T23:55:46.054Z] -- The CXX compiler identification is MSVC 19.29.30038.1[2022-02-06T23:55:46.054Z] -- Detecting C compiler ABI info[2022-02-06T23:55:47.014Z] -- Detecting C compiler ABI info - done[2022-02-06T23:55:47.296Z] -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.29.30037/bin/Hostx64/x64/cl.exe - skipped[2022-02-06T23:55:47.296Z] -- Detecting C compile features[2022-02-06T23:55:47.296Z] -- Detecting C compile features - done[2022-02-06T23:55:47.296Z] -- Detecting CXX compiler ABI info[2022-02-06T23:55:47.871Z] -- Detecting CXX compiler ABI info - done[2022-02-06T23:55:47.871Z] -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.29.30037/bin/Hostx64/x64/cl.exe - skipped[2022-02-06T23:55:47.871Z] -- Detecting CXX compile features[2022-02-06T23:55:47.871Z] -- Detecting CXX compile features - done[2022-02-06T23:55:47.871Z] Installing in C:/CI/Software Installs/kirigami. Run C:/CI/Job Build/build/prefix.sh to set the environment for kirigami2.[2022-02-06T23:55:47.871Z] Installing in C:/CI/Software Installs/kirigami. Run C:/CI/Job Build/build/prefix.sh to set the environment for kirigami2.[2022-02-06T23:55:47.871Z] -- Could not set up the appstream test. appstreamcli is missing.[2022-02-06T23:55:47.871Z] fatal: HEAD does not point to a branch[2022-02-06T23:55:47.871Z] -- Looking for __GLIBC__[2022-02-06T23:55:48.134Z] -- Looking for __GLIBC__ - not found[2022-02-06T23:55:48.134Z] -- Performing Test BSYMBOLICFUNCTIONS_AVAILABLE[2022-02-06T23:55:49.086Z] -- Performing Test BSYMBOLICFUNCTIONS_AVAILABLE - Success[2022-02-06T23:55:51.645Z] -- Found QtGraphicalEffects-QMLModule: TRUE (found version "") [2022-02-06T23:55:51.645Z] -- Performing Test COMPILER_HAS_DEPRECATED_ATTR[2022-02-06T23:55:51.645Z] -- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Failed[2022-02-06T23:55:51.645Z] -- Performing Test COMPILER_HAS_DEPRECATED[2022-02-06T23:55:52.622Z] -- Performing Test COMPILER_HAS_DEPRECATED - Success[2022-02-06T23:55:52.622Z] -- Found Doxygen: C:/Craft/CI-Qt515/windows-msvc2019_64-cl-debug/dev-utils/bin/doxygen.exe (found suitable version "1.9.1 (ef9b20ac7f8a8621fcfc299f8bd0b80422390f4b)", minimum required is "1.8.13") found components: doxygen missing components: dot[2022-02-06T23:55:52.622Z] -- Found QHelpGenerator executable: C:/Craft/CI-Qt515/windows-msvc2019_64-cl-debug/bin/qhelpgenerator.exe[2022-
KDE CI: Frameworks » kirigami » kf5-qt5 WindowsMSVCQt5.15 - Build # 661 - Still Failing!
BUILD FAILURE Build URL https://build.kde.org/job/Frameworks/job/kirigami/job/kf5-qt5%20WindowsMSVCQt5.15/661/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Sun, 06 Feb 2022 23:55:56 + Build duration: 17 sec and counting CONSOLE OUTPUT [...truncated 186 lines...][2022-02-06T23:56:06.377Z] __VSCMD_PREINIT_PATH = 'C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\Python38\Scripts\;C:\Program Files\Python38\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Git\cmd;C:\Users\Jenkins\AppData\Local\Microsoft\WindowsApps'[2022-02-06T23:56:06.377Z] __VSCMD_SCRIPT_ERR_COUNT = '0'[2022-02-06T23:56:06.377Z] CMAKE_PREFIX_PATH = 'C:\CI\Software Installs\kirigami;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\dev-utils'[2022-02-06T23:56:06.377Z] XDG_DATA_DIRS = 'C:\CI\Software Installs\kirigami\share;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\share;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\dev-utils\share'[2022-02-06T23:56:06.377Z] PKG_CONFIG_PATH = 'C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\lib\pkgconfig;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\dev-utils\lib\pkgconfig'[2022-02-06T23:56:06.377Z] QT_PLUGIN_PATH= 'C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\lib\qca-qt5;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\bin\plugins'[2022-02-06T23:56:06.377Z] QMAKEFEATURES = 'C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\mkspecs/features'[2022-02-06T23:56:06.377Z] QT_DATA_DIRS = 'C:\CI\Software Installs\kirigami\share;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\share;C:\Craft\CI-Qt515\windows-msvc2019_64-cl-debug\dev-utils\share'[2022-02-06T23:56:06.377Z] XDG_CURRENT_DESKTOP = 'KDE'[2022-02-06T23:56:06.377Z] ASAN_OPTIONS = 'detect_leaks=0:new_delete_type_mismatch=0:detect_odr_violation=0:stack-use-after-scope=0:alloc_dealloc_mismatch=0'[2022-02-06T23:56:06.377Z] [2022-02-06T23:56:06.377Z] [2022-02-06T23:56:06.377Z] == Commencing Configuration:[2022-02-06T23:56:06.377Z] cmake -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTING=ON -DCMAKE_INSTALL_PREFIX="C:/CI/Software Installs/kirigami/" -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -G "Ninja" -DBUILD_QCH=TRUE -DBUILD_EXAMPLES=ON "C:\CI\Job Build"[2022-02-06T23:56:06.638Z] -- The C compiler identification is MSVC 19.29.30038.1[2022-02-06T23:56:07.247Z] -- The CXX compiler identification is MSVC 19.29.30038.1[2022-02-06T23:56:07.247Z] -- Detecting C compiler ABI info[2022-02-06T23:56:07.826Z] -- Detecting C compiler ABI info - done[2022-02-06T23:56:07.826Z] -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.29.30037/bin/Hostx64/x64/cl.exe - skipped[2022-02-06T23:56:07.826Z] -- Detecting C compile features[2022-02-06T23:56:07.826Z] -- Detecting C compile features - done[2022-02-06T23:56:07.826Z] -- Detecting CXX compiler ABI info[2022-02-06T23:56:08.397Z] -- Detecting CXX compiler ABI info - done[2022-02-06T23:56:08.397Z] -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.29.30037/bin/Hostx64/x64/cl.exe - skipped[2022-02-06T23:56:08.397Z] -- Detecting CXX compile features[2022-02-06T23:56:08.397Z] -- Detecting CXX compile features - done[2022-02-06T23:56:08.397Z] Installing in C:/CI/Software Installs/kirigami. Run C:/CI/Job Build/build/prefix.sh to set the environment for kirigami2.[2022-02-06T23:56:08.658Z] Installing in C:/CI/Software Installs/kirigami. Run C:/CI/Job Build/build/prefix.sh to set the environment for kirigami2.[2022-02-06T23:56:08.658Z] -- Could not set up the appstream test. appstreamcli is missing.[2022-02-06T23:56:08.658Z] fatal: HEAD does not point to a branch[2022-02-06T23:56:08.658Z] -- Looking for __GLIBC__[2022-02-06T23:56:08.658Z] -- Looking for __GLIBC__ - not found[2022-02-06T23:56:08.658Z] -- Performing Test BSYMBOLICFUNCTIONS_AVAILABLE[2022-02-06T23:56:09.228Z] -- Performing Test BSYMBOLICFUNCTIONS_AVAILABLE - Success[2022-02-06T23:56:11.182Z] -- Found QtGraphicalEffects-QMLModule: TRUE (found version "") [2022-02-06T23:56:11.182Z] -- Performing Test COMPILER_HAS_DEPRECATED_ATTR[2022-02-06T23:56:11.182Z] -- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Failed[2022-02-06T23:56:11.182Z] -- Performing Test COMPILER_HAS_DEPRECATED[2022-02-06T23:56:12.162Z] -- Performing Test COMPILER_HAS_DEPRECATED - Success[2022-02-06T23:56:12.162Z] -- Found Doxygen: C:/Craft/CI-Qt515/windows-msvc2019_64-cl-debug/dev-utils/bin/doxygen.exe (found suitable version "1.9.1 (ef9b20ac7f8a8621fcfc299f8bd0b80422390f4b)", minimum required is "1.8.13") found components: doxygen missing components: dot[2022-02-06T23:56:12.162Z] -- Found QHelpGenerator executable: C:/Craft/CI-Qt515/windows-msvc2019_64-cl-debug/bin/qhelpgenerator.exe[2022-
KDE CI: Frameworks » kirigami » kf5-qt5 FreeBSDQt5.15 - Build # 763 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kirigami/job/kf5-qt5%20FreeBSDQt5.15/763/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sun, 06 Feb 2022 23:55:33 + Build duration: 46 sec and counting JUnit Tests Name: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515 Failed: 16 test(s), Passed: 0 test(s), Skipped: 0 test(s), Total: 16 test(s)Failed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.pagepool/tst_layers.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.pagepool/tst_pagepool.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.tst_actiontoolbar.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.tst_avatar.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.tst_icon.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.tst_keynavigation.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.tst_listskeynavigation.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.tst_mnemonicdata.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.tst_pagerouter.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.tst_pagerow.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.tst_routerwindow.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.tst_theme.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.wheelhandler/tst_filterMouseEvents.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.wheelhandler/tst_invokables.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.wheelhandler/tst_onWheel.qmlFailed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.wheelhandler/tst_scrolling.qml
Kirigami Respin
Hi, Any chance of a respin for Kirigami? https://invent.kde.org/frameworks/ kirigami/-/commit/5e2416257bc5b07d3468647204671a6d360fbd1b fixes an issue where some files are installed to the wrong location. Thanks, Arjen
