Re: Critical Denial of Service bugs in Discover
On Mon, Feb 21, 2022 at 11:05 AM Ben Cooksley wrote: > > On Mon, Feb 21, 2022 at 10:01 PM Harald Sitter wrote: >> >> On Thu, Feb 10, 2022 at 1:11 PM Aleix Pol wrote: >> > >> > On Thu, Feb 10, 2022 at 11:05 AM Ben Cooksley wrote: >> > > >> > > >> > > >> > > On Thu, Feb 10, 2022 at 8:20 AM Aleix Pol wrote: >> > >> >> > >> [Snip] >> > >> >> > >> We still haven't discussed here is how to prevent this problem from >> > >> happening again. >> > >> >> > >> If we don't have information about what is happening, we cannot fix >> > >> problems. >> > > >> > > >> > > Part of the issue here is that the problem only came to Sysadmin >> > > attention very recently, when the system ran out of disk space as a >> > > result of growing log files. >> > > It was at that point we realised we had a serious problem. >> > > >> > > Prior to that the system load hadn't climbed to dangerous levels (> >> > > number of CPU cores) and Apache was keeping up with the traffic, so none >> > > of our other monitoring was tripped. >> > > >> > > If you have any thoughts on what sort of information you are thinking of >> > > that would be helpful. >> > >> > We could have plots of the amount of queries we get with a KNewStuff/* >> > user-agent over time and their distribution. >> > >> > > It would definitely be helpful though to know when new software is going >> > > to be released that will be interacting with the servers as we will then >> > > be able to monitor for abnormalities. >> > >> > We make big announcements of every Plasma release... (?) >> > >> > >> Is there anything that could be done in this front? The issue here >> > >> could have been addressed months ago, we just never knew it was >> > >> happening. >> > > >> > > >> > > One possibility that did occur to me today would be for us to integrate >> > > some kind of killswitch that our applications would check on first >> > > initialisation of functionality that talks to KDE.org servers. >> > > This would allow us to disable the functionality in question on user >> > > systems. >> > > >> > > The check would only be done on first initialization to keep load low, >> > > while still ensuring all users eventually are affected by the killswitch >> > > (as they will eventually need to logout/reboot for some reason or >> > > another). >> > > >> > > The killswitch would probably work best if it had some kind of version >> > > check in it so we could specify which versions are disabled. >> > > That would allow for subsequent updates - once delivered by >> > > distributions - to restore the functionality (while leaving it disabled >> > > for those who haven't updated). >> > >> > The file we are serving here effectively is the kill switch to all of >> > KNewStuff. >> >> I'm a bit late to the party but for future reference I think this >> was/is an architectural scaling problem on the server side as much as >> a bug on the client. If just https load is the problem then the >> "hotfix" is to use a HTTP load balancer until fixes make it into the >> clients, killing the clients is like the last resort ever. I'm sure we >> have the money to afford a bunch of cloud nodes serving as selective >> proxy caches for a month to balance out the KNS load on the canonical >> server. > > > This was a multi-fold bug: > > 1) Sysadmin allowing a compatibility endpoint to remain alive for years after > we told people to stop using it and to use the new one (which is on a CDN and > which would have handled this whole issue much better) > 2) Developers writing code to talk to KDE.org infrastructure without > consulting Sysadmin, especially where it deviated from previously established > patterns. > > In terms of scalability I disagree - the system is not being used here in a > manner for which it was not designed. > > This system is intended to serve downloads of KDE software and associated > data files to distributors and end users. These are actions that are expected > to: > a) Be undertaken on an infrequent basis; and > b) Be undertaken as a result of user initiated action (such as clicking a > download link) > > It was never intended to be used to serve configuration data files to end > user systems. We have autoconfig.kde.org for that. I'm not saying it should be. I'm saying instead of crippling our software we should have made the architecture on the other end scale as a hotfix and then fix the actual bug - that can still be hurried along, I'm sure the involved developers would have been entirely appreciative of the severity. The hip shooting doomsdaying I've seen instead can surely only have demotivated people and came over as unjustly aggressive and I'm sure peoples motivation to work on our software in general has greatly suffered as a result. If we removed features because they occasionally have bugs we may as well pack up shop and stop making software altogether. > The system in question is handling the load extremely well and far beyond my > expectations - it is fairly un
Re: Critical Denial of Service bugs in Discover
On Fri, Feb 25, 2022 at 10:09 PM Harald Sitter wrote: > On Mon, Feb 21, 2022 at 11:05 AM Ben Cooksley wrote: > > > > On Mon, Feb 21, 2022 at 10:01 PM Harald Sitter wrote: > >> > >> On Thu, Feb 10, 2022 at 1:11 PM Aleix Pol wrote: > >> > > >> > On Thu, Feb 10, 2022 at 11:05 AM Ben Cooksley > wrote: > >> > > > >> > > > >> > > > >> > > On Thu, Feb 10, 2022 at 8:20 AM Aleix Pol wrote: > >> > >> > >> > >> [Snip] > >> > >> > >> > >> We still haven't discussed here is how to prevent this problem from > >> > >> happening again. > >> > >> > >> > >> If we don't have information about what is happening, we cannot > fix problems. > >> > > > >> > > > >> > > Part of the issue here is that the problem only came to Sysadmin > attention very recently, when the system ran out of disk space as a result > of growing log files. > >> > > It was at that point we realised we had a serious problem. > >> > > > >> > > Prior to that the system load hadn't climbed to dangerous levels (> > number of CPU cores) and Apache was keeping up with the traffic, so none of > our other monitoring was tripped. > >> > > > >> > > If you have any thoughts on what sort of information you are > thinking of that would be helpful. > >> > > >> > We could have plots of the amount of queries we get with a KNewStuff/* > >> > user-agent over time and their distribution. > >> > > >> > > It would definitely be helpful though to know when new software is > going to be released that will be interacting with the servers as we will > then be able to monitor for abnormalities. > >> > > >> > We make big announcements of every Plasma release... (?) > >> > > >> > >> Is there anything that could be done in this front? The issue here > >> > >> could have been addressed months ago, we just never knew it was > >> > >> happening. > >> > > > >> > > > >> > > One possibility that did occur to me today would be for us to > integrate some kind of killswitch that our applications would check on > first initialisation of functionality that talks to KDE.org servers. > >> > > This would allow us to disable the functionality in question on > user systems. > >> > > > >> > > The check would only be done on first initialization to keep load > low, while still ensuring all users eventually are affected by the > killswitch (as they will eventually need to logout/reboot for some reason > or another). > >> > > > >> > > The killswitch would probably work best if it had some kind of > version check in it so we could specify which versions are disabled. > >> > > That would allow for subsequent updates - once delivered by > distributions - to restore the functionality (while leaving it disabled for > those who haven't updated). > >> > > >> > The file we are serving here effectively is the kill switch to all of > KNewStuff. > >> > >> I'm a bit late to the party but for future reference I think this > >> was/is an architectural scaling problem on the server side as much as > >> a bug on the client. If just https load is the problem then the > >> "hotfix" is to use a HTTP load balancer until fixes make it into the > >> clients, killing the clients is like the last resort ever. I'm sure we > >> have the money to afford a bunch of cloud nodes serving as selective > >> proxy caches for a month to balance out the KNS load on the canonical > >> server. > > > > > > This was a multi-fold bug: > > > > 1) Sysadmin allowing a compatibility endpoint to remain alive for years > after we told people to stop using it and to use the new one (which is on a > CDN and which would have handled this whole issue much better) > > 2) Developers writing code to talk to KDE.org infrastructure without > consulting Sysadmin, especially where it deviated from previously > established patterns. > > > > In terms of scalability I disagree - the system is not being used here > in a manner for which it was not designed. > > > > This system is intended to serve downloads of KDE software and > associated data files to distributors and end users. These are actions that > are expected to: > > a) Be undertaken on an infrequent basis; and > > b) Be undertaken as a result of user initiated action (such as clicking > a download link) > > > > It was never intended to be used to serve configuration data files to > end user systems. We have autoconfig.kde.org for that. > > I'm not saying it should be. I'm saying instead of crippling our > software we should have made the architecture on the other end scale > as a hotfix and then fix the actual bug - that can still be hurried > along, I'm sure the involved developers would have been entirely > appreciative of the severity. The hip shooting doomsdaying I've seen > instead can surely only have demotivated people and came over as > unjustly aggressive and I'm sure peoples motivation to work on our > software in general has greatly suffered as a result. If we removed > features because they occasionally have bugs we may as well pack up > shop and stop making software altogether. > The '
KDE CI: Frameworks » purpose » kf5-qt5 FreeBSDQt5.15 - Build # 199 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/purpose/job/kf5-qt5%20FreeBSDQt5.15/199/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Fri, 25 Feb 2022 20:35:13 + Build duration: 1 min 47 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 2 test(s)Failed: projectroot.autotests.menutest
KDE CI: Frameworks » purpose » kf5-qt5 FreeBSDQt5.15 - Build # 200 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/purpose/job/kf5-qt5%20FreeBSDQt5.15/200/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Fri, 25 Feb 2022 20:37:33 + Build duration: 1 min 8 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 2 test(s)Failed: projectroot.autotests.menutest
KDE CI: Frameworks » purpose » kf5-qt5 SUSEQt5.15 - Build # 212 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/purpose/job/kf5-qt5%20SUSEQt5.15/212/ Project: kf5-qt5 SUSEQt5.15 Date of build: Fri, 25 Feb 2022 20:35:13 + Build duration: 4 min 0 sec and counting BUILD ARTIFACTS acc/KF5Purpose-5.92.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: 1 test(s), Skipped: 0 test(s), Total: 2 test(s)Failed: projectroot.autotests.menutest Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report13% (3/24)20% (10/50)20% (10/50)17% (371/2170)16% (159/993)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests50% (1/2)50% (1/2)73% (107/146)48% (62/128)src89% (8/9)89% (8/9)59% (230/389)41% (73/177)src.externalprocess0% (0/2)0% (0/2)0% (0/137)0% (0/98)src.fileitemactionplugin0% (0/1)0% (0/1)0% (0/34)0% (0/26)src.plugins.barcode0% (0/1)0% (0/1)0% (0/5)100% (0/0)src.plugins.bluetooth0% (0/1)0% (0/1)0% (0/35)0% (0/8)src.plugins.email0% (0/1)0% (0/1)0% (0/48)0% (0/30)src.plugins.imgur0% (0/2)0% (0/2)0% (0/188)0% (0/61)src.plugins.kdeconnect0% (0/1)0% (0/1)0% (0/35)0% (0/6)src.plugins.kdeconnect_sms0% (0/1)0% (0/1)0% (0/17)0% (0/2)src.plugins.ktp-sendfile0% (0/1)0% (0/1)0% (0/29)0% (0/6)src.plugins.pastebin0% (0/1)0% (0/1)0% (0/58)0% (0/23)src.plugins.phabricator0% (0/3)0% (0/3)0% (0/223)0% (0/74)src.plugins.phabricator.quick0% (0/5)0% (0/5)0% (0/96)0% (0/48)src.plugins.phabricator.tests0% (0/1)0% (0/1)0% (0/63)0% (0/22)src.plugins.reviewboard0% (0/3)0% (0/3)0% (0/252)0% (0/70)src.plugins.reviewboard.quick0% (0/7)0% (0/7)0% (0/163)0% (0/80)src.plugins.saveas100% (1/1)10
KDE CI: Frameworks » purpose » kf5-qt5 SUSEQt5.15 - Build # 213 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/purpose/job/kf5-qt5%20SUSEQt5.15/213/ Project: kf5-qt5 SUSEQt5.15 Date of build: Fri, 25 Feb 2022 20:39:15 + Build duration: 2 min 32 sec and counting BUILD ARTIFACTS acc/KF5Purpose-5.92.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: 1 test(s), Skipped: 0 test(s), Total: 2 test(s)Failed: projectroot.autotests.menutest Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report13% (3/24)20% (10/50)20% (10/50)17% (371/2170)16% (159/993)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests50% (1/2)50% (1/2)73% (107/146)48% (62/128)src89% (8/9)89% (8/9)59% (230/389)41% (73/177)src.externalprocess0% (0/2)0% (0/2)0% (0/137)0% (0/98)src.fileitemactionplugin0% (0/1)0% (0/1)0% (0/34)0% (0/26)src.plugins.barcode0% (0/1)0% (0/1)0% (0/5)100% (0/0)src.plugins.bluetooth0% (0/1)0% (0/1)0% (0/35)0% (0/8)src.plugins.email0% (0/1)0% (0/1)0% (0/48)0% (0/30)src.plugins.imgur0% (0/2)0% (0/2)0% (0/188)0% (0/61)src.plugins.kdeconnect0% (0/1)0% (0/1)0% (0/35)0% (0/6)src.plugins.kdeconnect_sms0% (0/1)0% (0/1)0% (0/17)0% (0/2)src.plugins.ktp-sendfile0% (0/1)0% (0/1)0% (0/29)0% (0/6)src.plugins.pastebin0% (0/1)0% (0/1)0% (0/58)0% (0/23)src.plugins.phabricator0% (0/3)0% (0/3)0% (0/223)0% (0/74)src.plugins.phabricator.quick0% (0/5)0% (0/5)0% (0/96)0% (0/48)src.plugins.phabricator.tests0% (0/1)0% (0/1)0% (0/63)0% (0/22)src.plugins.reviewboard0% (0/3)0% (0/3)0% (0/252)0% (0/70)src.plugins.reviewboard.quick0% (0/7)0% (0/7)0% (0/163)0% (0/80)src.plugins.saveas100% (1/1)1
KDE CI: Frameworks » kio » kf5-qt5 SUSEQt5.15 - Build # 1408 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.15/1408/ Project: kf5-qt5 SUSEQt5.15 Date of build: Fri, 25 Feb 2022 21:32:29 + Build duration: 18 min and counting BUILD ARTIFACTS acc/KF5KIO-5.92.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: 60 test(s), Skipped: 0 test(s), Total: 61 test(s)Failed: projectroot.autotests.kiocore_jobtestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s) Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report61% (25/41)69% (298/429)69% (298/429)58% (39365/68032)42% (21810/52082)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests95% (61/64)95% (61/64)91% (11427/12493)46% (7190/15624)autotests.http100% (5/5)100% (5/5)99% (527/528)58% (167/290)autotests.kcookiejar100% (1/1)100% (1/1)94% (173/185)63% (70/112)src100% (1/1)100% (1/1)89% (8/9)71% (10/14)src.core88% (107/121)88% (107/121)61% (9390/15306)52% (4640/8886)src.core.kssl100% (1/1)100% (1/1)38% (33/86)50% (2/4)src.filewidgets79% (31/39)79% (31/39)58% (5405/9396)44% (2324/5325)src.gui100% (11/11)100% (11/11)73% (867/1188)58% (458/790)src.gui.systemd50% (2/4)50% (2/4)4% (7/178)1% (1/108)src.ioslaves.file100% (7/7)100% (7/7)56% (785/1400)42% (518/1227)src.ioslaves.file.kauth0% (0/2)0% (0/2)0% (0/187)0% (0/83)src.ioslaves.ftp100% (2/2)100% (2/2)40% (551/1380)30% (435/1430)src.ioslaves.help0% (0/5)0% (0/5)0% (0/253)0% (0/138)src.ioslaves.http88% (7/8)88% (7/8)43% (1873/4354)37% (1358/3719)src.ioslaves.http.kcookiejar40% (2/5)40% (2/5)49% (664/1364)56% (588/1053)src.ioslaves.remote100% (2/2)100% (2/2)25%
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1425 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1425/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Fri, 25 Feb 2022 21:32:29 + Build duration: 24 min and counting JUnit Tests Name: projectroot Failed: 6 test(s), Passed: 54 test(s), Skipped: 0 test(s), Total: 60 test(s)Failed: projectroot.autotests.applicationlauncherjob_forkingtestFailed: projectroot.autotests.applicationlauncherjob_scopetestFailed: projectroot.autotests.commandlauncherjob_servicetestFailed: projectroot.autotests.kiocore_jobtestFailed: 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 » kcoreaddons » kf5-qt5 FreeBSDQt5.15 - Build # 414 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kcoreaddons/job/kf5-qt5%20FreeBSDQt5.15/414/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Fri, 25 Feb 2022 23:50:15 + Build duration: 1 min 48 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 32 test(s), Skipped: 0 test(s), Total: 33 test(s)Failed: projectroot.autotests.klistopenfilesjobtest_unix
KDE CI: Frameworks » kcoreaddons » kf5-qt5 FreeBSDQt5.15 - Build # 415 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kcoreaddons/job/kf5-qt5%20FreeBSDQt5.15/415/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Fri, 25 Feb 2022 23:52:05 + Build duration: 1 min 40 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 32 test(s), Skipped: 0 test(s), Total: 33 test(s)Failed: projectroot.autotests.klistopenfilesjobtest_unix
KDE CI: Frameworks » kauth » kf5-qt5 WindowsMSVCQt5.15 - Build # 116 - Failure!
BUILD FAILURE
Build URL
https://build.kde.org/job/Frameworks/job/kauth/job/kf5-qt5%20WindowsMSVCQt5.15/116/
Project:
kf5-qt5 WindowsMSVCQt5.15
Date of build:
Sat, 26 Feb 2022 00:00:02 +
Build duration:
24 min and counting
JUnit Tests
Name: projectroot Failed: 1 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 2 test(s)Failed: projectroot.autotests.KAuthHelperTest
CONSOLE OUTPUT
[...truncated 431 lines...][2022-02-26T00:12:49.964Z]Site: [2022-02-26T00:12:49.964Z]Build name: (empty)[2022-02-26T00:12:49.964Z] Create new tag: 20220226-0012 - Experimental[2022-02-26T00:12:49.964Z] Cannot find file: C:/CI/Job Build/build/DartConfiguration.tcl[2022-02-26T00:12:49.964Z] Test project C:/CI/Job Build/build[2022-02-26T00:12:49.964Z] Start 1: KAuthSetupActionTest[2022-02-26T00:12:51.888Z] 1/2 Test #1: KAuthSetupActionTest . Passed2.30 sec[2022-02-26T00:12:51.888Z] Start 2: KAuthHelperTest[2022-02-26T00:22:58.928Z] 2/2 Test #2: KAuthHelperTest ..***Timeout 599.95 sec[2022-02-26T00:22:58.928Z] * Start testing of HelperTest *[2022-02-26T00:22:58.929Z] Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-llp64 shared (dynamic) debug build; by MSVC 2019), windows 10[2022-02-26T00:22:58.929Z] QDEBUG : HelperTest::initTestCase() Test backend loaded[2022-02-26T00:22:58.929Z] QDEBUG : HelperTest::initTestCase() Waiting for HelperHandler to be initialized[2022-02-26T00:22:58.929Z] QDEBUG : HelperTest::initTestCase() Initializing helper handler[2022-02-26T00:22:58.929Z] QWARN : HelperTest::initTestCase() kf.auth: Error registering helper DBus service "org.kde.kf5auth.autotest" "Not connected to D-Bus server"[2022-02-26T00:22:58.929Z] FAIL! : HelperTest::initTestCase() 'm_helperProxy->initHelper(QLatin1String("org.kde.kf5auth.autotest"))' returned FALSE. ()[2022-02-26T00:22:58.929Z] ..\autotests\HelperTest.cpp(109) : failure location[2022-02-26T00:22:58.929Z] [2022-02-26T00:22:58.929Z] [2022-02-26T00:22:58.929Z] 50% tests passed, 1 tests failed out of 2[2022-02-26T00:22:58.929Z] [2022-02-26T00:22:58.929Z] Total Test time (real) = 602.32 sec[2022-02-26T00:22:58.929Z] [2022-02-26T00:22:58.929Z] The following tests FAILED:[2022-02-26T00:22:58.929Z] 2 - KAuthHelperTest (Timeout)[2022-02-26T00:22:58.929Z] Errors while running CTest[2022-02-26T00:22:58.929Z] ERROR: The process "kded5.exe" not found.[2022-02-26T00:22:58.929Z] ERROR: The process "klauncher.exe" not found.[2022-02-26T00:22:58.929Z] ERROR: The process "kdeinit5.exe" not found.[2022-02-26T00:22:58.929Z] ERROR: The process "test_crasher.exe" not found.[2022-02-26T00:22:58.929Z] ERROR: The process "testremoterunner.exe" not found.[2022-02-26T00:22:58.929Z] ERROR: The process "dbus-daemon.exe" not found.[2022-02-26T00:23:25.563Z] ERROR: The process "kioslave.exe" not found.[2022-02-26T00:23:25.563Z] ERROR: The process "kioslave5.exe" not found.[2022-02-26T00:23:25.563Z] ERROR: The process "vctip.exe" not found.[2022-02-26T00:23:33.722Z] ERROR: The process "kioslave5.exe" not found.[Pipeline] junit[2022-02-26T00:23:33.739Z] Recording test results[2022-02-26T00:24:31.142Z] [Checks API] No suitable checks publisher found.[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Capturing Installation)[Pipeline] bat[2022-02-26T00:24:43.655Z] [2022-02-26T00:24:43.655Z] C:\CI\Job Build>python -u ci-tooling/helpers/capture-install.py --product Frameworks --project kauth --branchGroup kf5-qt5 --environment production --platform WindowsMSVCQt5.15 --divertedTo "C:/CI/Job Build/install-divert/" --installedTo "C:/CI/Software Installs/kauth/" [2022-02-26T00:25:01.810Z] Exception: Error reading SSH protocol banner[2022-02-26T00:25:01.810Z] Traceback (most recent call last):[2022-02-26T00:25:01.810Z] File "C:\Program Files\Python38\lib\site-packages\paramiko\transport.py", line 2211, in _check_banner[2022-02-26T00:25:01.810Z] buf = self.packetizer.readline(timeout)[2022-02-26T00:25:01.810Z] File "C:\Program Files\Python38\lib\site-packages\paramiko\packet.py", line 380, in readline[2022-02-26T00:25:01.810Z] buf += self._read_timeout(timeout)[2022-02-26T00:25:01.810Z] File "C:\Program Files\Python38\lib\site-packages\paramiko\packet.py", line 622, in _read_timeout[2022-02-26T00:25:01.810Z] raise socket.timeout()[2022-02-26T00:25:01.810Z] socket.timeout[2022-02-26T00:25:01.810Z] [2022-02-26T00:25:01.810Z] During handling of the above exception, another exception occurred:[2022-02-26T00:25:01.810Z] [2022-02-26T00:25:01.810Z] Traceback (most recent call last):[2022-02-26T00:25:01.810Z] File "C:\Program Files\Python38\lib\site-packages\paramiko\transport.py", line 2039, in run[2022-02-26T00:25:01.810Z] self._check_banner()[2022-02-26T00:25:01.810Z] File "C:\Program Files\Python38\lib\site-packages\paramiko\transport.py", line 2215, in _check_banner[2022-02-26T00:25:01.810Z] raise SSHException([2022-02-26T00:
KDE CI: Frameworks » kauth » kf5-qt5 WindowsMSVCQt5.15 - Build # 117 - Still unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kauth/job/kf5-qt5%20WindowsMSVCQt5.15/117/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Sat, 26 Feb 2022 00:25:52 + Build duration: 38 min and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 2 test(s)Failed: projectroot.autotests.KAuthHelperTest
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1426 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1426/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sat, 26 Feb 2022 01:48:08 + Build duration: 10 min and counting JUnit Tests Name: projectroot Failed: 4 test(s), Passed: 56 test(s), Skipped: 0 test(s), Total: 60 test(s)Failed: projectroot.autotests.applicationlauncherjob_forkingtestFailed: projectroot.autotests.kiocore_ktcpsockettestFailed: projectroot.autotests.kiowidgets_kdirlistertestFailed: projectroot.autotests.kiowidgets_kdirmodeltestName: 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 SUSEQt5.15 - Build # 1409 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.15/1409/ Project: kf5-qt5 SUSEQt5.15 Date of build: Sat, 26 Feb 2022 01:48:07 + Build duration: 12 min and counting BUILD ARTIFACTS acc/KF5KIO-5.92.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: 61 test(s), Skipped: 0 test(s), Total: 61 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) Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report61% (25/41)69% (298/429)69% (298/429)58% (39361/68032)42% (21774/52082)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests95% (61/64)95% (61/64)91% (11427/12493)46% (7161/15624)autotests.http100% (5/5)100% (5/5)99% (527/528)58% (167/290)autotests.kcookiejar100% (1/1)100% (1/1)94% (173/185)63% (70/112)src100% (1/1)100% (1/1)89% (8/9)71% (10/14)src.core88% (107/121)88% (107/121)61% (9389/15306)52% (4637/8886)src.core.kssl100% (1/1)100% (1/1)38% (33/86)50% (2/4)src.filewidgets79% (31/39)79% (31/39)58% (5407/9397)44% (2322/5325)src.gui100% (11/11)100% (11/11)73% (867/1188)58% (458/790)src.gui.systemd50% (2/4)50% (2/4)4% (7/178)1% (1/108)src.ioslaves.file100% (7/7)100% (7/7)56% (785/1400)42% (518/1227)src.ioslaves.file.kauth0% (0/2)0% (0/2)0% (0/187)0% (0/83)src.ioslaves.ftp100% (2/2)100% (2/2)40% (551/1380)30% (435/1430)src.ioslaves.help0% (0/5)0% (0/5)0% (0/253)0% (0/138)src.ioslaves.http88% (7/8)88% (7/8)43% (1873/4354)37% (1359/3719)src.ioslaves.http.kcookiejar40% (2/5)40% (2/5)49% (664/1364)56% (588/1053)src.ioslaves.remote100% (2/2)100% (2/2)25% (57/224)7
