Re: AudioTube in KDEReview
On Mittwoch, 16. Juni 2021 22:52:05 CEST Jonah Brüchert wrote: > > > - app isn't kcrash enabled :(( > > That would mean I have to use bugzilla? How would I create a product > there, and do I have to manually add each new version there? To create a new product open a sysadmin ticket and ask for it (https://go.kde.org/u/systickets) If you follow the release pattern (https://community.kde.org/ReleasingSoftware) then the releaseme script will provide a template for another sysadmin ticket which contains the request to add that new version to bugzilla. > I wasn't able to find any documentation on that. I CC this mail to the new documentation contractor so that he knows about the lack. -- Regards Thomas Baumgart https://www.signal.org/ Signal, the better WhatsApp - Computers are like air conditioners: they stop working properly if you open WINDOWS (anonymous source) - signature.asc Description: This is a digitally signed message part.
KDE CI: Frameworks » attica » kf5-qt5 SUSEQt5.15 - Build # 69 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/attica/job/kf5-qt5%20SUSEQt5.15/69/ Project: kf5-qt5 SUSEQt5.15 Date of build: Thu, 17 Jun 2021 01:27:46 + Build duration: 3 min 7 sec and counting BUILD ARTIFACTS acc/KF5Attica-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: 4 test(s), Skipped: 0 test(s), Total: 5 test(s)Failed: projectroot.autotests.providertest Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report67% (2/3)23% (18/77)23% (18/77)14% (562/4059)11% (216/1960)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests100% (3/3)100% (3/3)72% (89/124)36% (25/70)src21% (15/72)21% (15/72)13% (473/3638)11% (191/1818)tests.projecttest0% (0/2)0% (0/2)0% (0/297)0% (0/72)
KDE CI: Frameworks » attica » kf5-qt5 FreeBSDQt5.15 - Build # 65 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/attica/job/kf5-qt5%20FreeBSDQt5.15/65/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Thu, 17 Jun 2021 01:27:46 + Build duration: 1 min 36 sec and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)
Re: Notice of withdrawal of CI services: KDevelop and KDE Connect
Hi, This is indeed an issue that has occurred previously, and actually I've written to you, Ben, once before about this. Now I'm asking again, why is it necessary to email *FIVE* mailing lists for issues that are primarily solved by a much much smaller subgroup of people? Maybe send it to a few C++ lists as well, maybe someone'll jump out and fix the CI 浪 On a very related topic, for the third time, send the kdeconnect CI status emails to the actual developers and contributors for whom they are actionable, not the entire kdeconnect mailing list. It's just noise for the majority of non-code contributors, non-code contributors that might be able to help with support questions but who are very likely ignoring the list due to horrifically bad SNR. Have an extra day, Avamander On Wed, Jun 16, 2021 at 9:29 PM Ben Cooksley wrote: > Hi all, > > The following is notice that I intend to withdraw CI services from the > following two KDE projects due to faults in their code or build system > which are having a significant adverse impact on the CI system and > negatively impacting on other projects: > > - KDevelop > - KDE Connect > > This withdrawal will be applied to all platforms. > > In the case of KDevelop, it has a series of unit tests which on FreeBSD > cause gdb to hang and consume an entire CPU core indefinitely. This slows > down builds for all other projects using that CI server, and also prevents > KWin tests from proceeding - completely blocking it's jobs. This fault is > in the debuggee_slow family of tests. > > As this issue has persisted for some time now despite being mentioned, I > require that the family of tests in question be disabled across all > platforms. > > In the case of KDE Connect, as part of it's configure process it runs an > external command that results in dbus-daemon being launched. This process > persists following the build and would only be cleaned up by our tooling > that runs tests. Should the compilation fail (as it does currently) it will > result in the CI builder being broken - which is why we have had so many > Windows builds fail lately. > > As this is an issue that has occurred previously, I require that the > configure time check which is launching dbus-daemon to be expunged from KDE > Connect. > > As a reminder to all projects, running commands that interact with > dbus-daemon or kdeinit is not permitted during configure or build time. > > Regards, > Ben Cooksley > KDE Sysadmin >
Re: Notice of withdrawal of CI services: KDevelop and KDE Connect
How about if we add a config flag for our ci machines and configure cmake of these 2 project's test to ignore building/adding those problematic tests whenever it saw those flags? I don't know why but it doesn't sound correct to me to kill the ci build of any project because of these types of problems. Ömer Fadıl Usta PGP key : 0xfd11561976b1690b about.me/omerusta Ben Cooksley , 16 Haz 2021 Çar, 21:57 tarihinde şunu yazdı: > On Thu, Jun 17, 2021 at 6:41 AM Nate Graham wrote: > >> This kind of problem will be generically solved for everyone once we get >> GitLab's pre-commit CI, which can block merging of MRs until the >> failures are resolved--so they actually *will* be resolved. How soon can >> we get that finally rolled out across KDE? >> > > I'm afraid GitLab CI wouldn't have prevented this from occurring - because > the pre-merge CI still needs to run somewhere. > The problem here is that the simple act of running the build > degrades/breaks the builders for everyone else. > > In terms of a timeline on this, once I have the situation with Nextcloud > sorted out (which had to be prioritised as the version we're on goes out of > support in the next few months) we'll hopefully be able to work on GitLab > CI (assuming another vendor of ours doesn't go and pull another major > dependency bump stunt like Nextcloud did) > > >> Until that happens, this sort of problem will recur infinitely because >> people will continue to miss or ignore CI failures because they send >> emails after merge/commit rather than before, and are formatted >> semi-incomprehensibly. >> >> Nate >> > > Regards, > Ben > > >> >> >> On 6/16/21 12:28 PM, Ben Cooksley wrote: >> > Hi all, >> > >> > The following is notice that I intend to withdraw CI services from the >> > following two KDE projects due to faults in their code or build system >> > which are having a significant adverse impact on the CI system and >> > negatively impacting on other projects: >> > >> > - KDevelop >> > - KDE Connect >> > >> > This withdrawal will be applied to all platforms. >> > >> > In the case of KDevelop, it has a series of unit tests which on FreeBSD >> > cause gdb to hang and consume an entire CPU core indefinitely. This >> > slows down builds for all other projects using that CI server, and also >> > prevents KWin tests from proceeding - completely blocking it's jobs. >> > This fault is in the debuggee_slow family of tests. >> > >> > As this issue has persisted for some time now despite being mentioned, >> I >> > require that the family of tests in question be disabled across all >> > platforms. >> > >> > In the case of KDE Connect, as part of it's configure process it runs >> an >> > external command that results in dbus-daemon being launched. This >> > process persists following the build and would only be cleaned up by >> our >> > tooling that runs tests. Should the compilation fail (as it does >> > currently) it will result in the CI builder being broken - which is why >> > we have had so many Windows builds fail lately. >> > >> > As this is an issue that has occurred previously, I require that the >> > configure time check which is launching dbus-daemon to be expunged from >> > KDE Connect. >> > >> > As a reminder to all projects, running commands that interact with >> > dbus-daemon or kdeinit is not permitted during configure or build time. >> > >> > Regards, >> > Ben Cooksley >> > KDE Sysadmin >> >
Re: Notice of withdrawal of CI services: KDevelop and KDE Connect
This kind of problem will be generically solved for everyone once we get GitLab's pre-commit CI, which can block merging of MRs until the failures are resolved--so they actually *will* be resolved. How soon can we get that finally rolled out across KDE? Until that happens, this sort of problem will recur infinitely because people will continue to miss or ignore CI failures because they send emails after merge/commit rather than before, and are formatted semi-incomprehensibly. Nate On 6/16/21 12:28 PM, Ben Cooksley wrote: Hi all, The following is notice that I intend to withdraw CI services from the following two KDE projects due to faults in their code or build system which are having a significant adverse impact on the CI system and negatively impacting on other projects: - KDevelop - KDE Connect This withdrawal will be applied to all platforms. In the case of KDevelop, it has a series of unit tests which on FreeBSD cause gdb to hang and consume an entire CPU core indefinitely. This slows down builds for all other projects using that CI server, and also prevents KWin tests from proceeding - completely blocking it's jobs. This fault is in the debuggee_slow family of tests. As this issue has persisted for some time now despite being mentioned, I require that the family of tests in question be disabled across all platforms. In the case of KDE Connect, as part of it's configure process it runs an external command that results in dbus-daemon being launched. This process persists following the build and would only be cleaned up by our tooling that runs tests. Should the compilation fail (as it does currently) it will result in the CI builder being broken - which is why we have had so many Windows builds fail lately. As this is an issue that has occurred previously, I require that the configure time check which is launching dbus-daemon to be expunged from KDE Connect. As a reminder to all projects, running commands that interact with dbus-daemon or kdeinit is not permitted during configure or build time. Regards, Ben Cooksley KDE Sysadmin
Re: AudioTube in KDEReview
- app isn't kcrash enabled :(( That would mean I have to use bugzilla? How would I create a product there, and do I have to manually add each new version there? I wasn't able to find any documentation on that. OpenPGP_0xA81E075ABEC80A7E.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Notice of withdrawal of CI services: KDevelop and KDE Connect
On Mittwoch, 16. Juni 2021 20:28:25 CEST Ben Cooksley wrote: > Hi all, > > The following is notice that I intend to withdraw CI services from the > following two KDE projects due to faults in their code or build system > which are having a significant adverse impact on the CI system and > negatively impacting on other projects: > > - KDevelop > - KDE Connect > > This withdrawal will be applied to all platforms. > > In the case of KDevelop, it has a series of unit tests which on FreeBSD > cause gdb to hang and consume an entire CPU core indefinitely. This slows > down builds for all other projects using that CI server, and also prevents > KWin tests from proceeding - completely blocking it's jobs. This fault is > in the debuggee_slow family of tests. Hey Ben, first time I hear of this issue. I simply don't have the capacity to track kdevelop CI mails, so if anything really bad happens, I would really appreciate if anyone who notices that sents a mail to the kdevelop mailing list so we can act on it. I still use kdevelop daily, but don't put any other work in it currently due to lack of time... That said: can we just disable it on the FreeBSD platform, if that's the only one that exhibits this failure? Alternatively I'm obviously fine with skipping that test on that platform, can you give me a link to a failure please so I can see which tests exactly are affected? Then I'll add the QSKIP + platform ifdef checks to skip it on freebsd. Cheers and thanks for letting me know about this problem -- Milian Wolff m...@milianw.de http://milianw.de signature.asc Description: This is a digitally signed message part.
Re: Notice of withdrawal of CI services: KDevelop and KDE Connect
On Mittwoch, 16. Juni 2021 20:28:25 CEST Ben Cooksley wrote: > Hi all, > > The following is notice that I intend to withdraw CI services from the > following two KDE projects due to faults in their code or build system > which are having a significant adverse impact on the CI system and > negatively impacting on other projects: > > - KDevelop > - KDE Connect > > This withdrawal will be applied to all platforms. > > In the case of KDevelop, it has a series of unit tests which on FreeBSD > cause gdb to hang and consume an entire CPU core indefinitely. This slows > down builds for all other projects using that CI server, and also prevents > KWin tests from proceeding - completely blocking it's jobs. This fault is > in the debuggee_slow family of tests. Hey Ben, first time I hear of this issue. I simply don't have the capacity to track kdevelop CI mails, so if anything really bad happens, I would really appreciate if anyone who notices that sents a mail to the kdevelop mailing list so we can act on it. I still use kdevelop daily, but don't put any other work in it currently due to lack of time... That said: can we just disable it on the FreeBSD platform, if that's the only one that exhibits this failure? Alternatively I'm obviously fine with skipping that test on that platform, can you give me a link to a failure please so I can see which tests exactly are affected? Then I'll add the QSKIP + platform ifdef checks to skip it on freebsd. Cheers and thanks for letting me know about this problem -- Milian Wolff m...@milianw.de http://milianw.de signature.asc Description: This is a digitally signed message part.
Re: AudioTube in KDEReview
Thank you for having a look. - seeking doesn't seem to do anything. I get `audiotube(103398)/(qml) onMoved: Value: 71454.30987821381` as output but then the seek doesn't actually happen This is a known QtMultimedia bug that also seems to affect other apps I heard. I don't think I can do anything about it. - something is also wonky with the playlist. it doesn't cover the width (when data fails to load). it is overlapped by the scrollbar. clear and shuffle don't seem to have labels though there would be enough space https://i.imgur.com/Q3IoaBj.png The left side should display the album cover, do you think the playlist should fill the whole page if there is none? - on some artists I get `TypeError: 'NoneType' object is not iterable ` https://i.imgur.com/U8BKHbQ.png Which exactly? I can't reproduce it with Daft Punk. - ytmusic.cpp forces LC_ALL to en_us, that seems a bit fishy and it doesn't explain why either The python code randomly fails if the encoding is not utf8, this was my attempt to work around that. I can add a comment. - PlaylistUtils looks like it maybe should be a namespace not a class. feel free to ignore me if you disagree true OpenPGP_0xA81E075ABEC80A7E.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
KDE CI: Frameworks » extra-cmake-modules » kf5-qt5 WindowsMSVCQt5.15 - Build # 154 - Still unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20WindowsMSVCQt5.15/154/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 16 Jun 2021 18:08:23 + Build duration: 1 hr 8 min 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: 2 test(s), Passed: 62 test(s), Skipped: 0 test(s), Total: 64 test(s)Failed: projectroot.tests.ECMAddTests.ecm_add_tests_multi_testsFailed: projectroot.tests.ECMAddTests.ecm_add_tests_single_testsName: projectroot.tests.ECMAddTests Failed: 2 test(s), Passed: 0 test(s), Skipped: 0 test(s), Total: 2 test(s)Failed: projectroot.tests.ECMAddTests.multi_tests.ecm_add_tests_did_run_multi_testsFailed: projectroot.tests.ECMAddTests.single_tests.ecm_add_tests_did_run_single_tests
Re: Notice of withdrawal of CI services: KDevelop and KDE Connect
Hi Ben, On 16.06.21 20:28, Ben Cooksley wrote: Hi all, The following is notice that I intend to withdraw CI services from the following two KDE projects due to faults in their code or build system which are having a significant adverse impact on the CI system and negatively impacting on other projects: - KDevelop - KDE Connect This withdrawal will be applied to all platforms. In the case of KDevelop, it has a series of unit tests which on FreeBSD cause gdb to hang and consume an entire CPU core indefinitely. This slows down builds for all other projects using that CI server, and also prevents KWin tests from proceeding - completely blocking it's jobs. This fault is in the debuggee_slow family of tests. As this issue has persisted for some time now despite being mentioned, I require that the family of tests in question be disabled across all platforms. In the case of KDE Connect, as part of it's configure process it runs an external command that results in dbus-daemon being launched. This process persists following the build and would only be cleaned up by our tooling that runs tests. Should the compilation fail (as it does currently) it will result in the CI builder being broken - which is why we have had so many Windows builds fail lately. As this is an issue that has occurred previously, I require that the configure time check which is launching dbus-daemon to be expunged from KDE Connect. As a reminder to all projects, running commands that interact with dbus-daemon or kdeinit is not permitted during configure or build time. Regards, Ben Cooksley KDE Sysadmin I think I know what causes the KDE Connect behavior. The CMake code calls 'ecm_find_qmlmodule(org.kde.people 1.0)', which results a call to 'qmlplugindump org.kde.kpeople 1.0' which causes parts of the KPeople code to be executed (PersonsModel in particular) which does some DBus things that then trigger dbus-daemon. As a stopgap solution to make the CI operational we can remove that ecm_find_qmlmodule call. In terms of a proper solution there was a recent effort to remove the mandatory DBus dependency from KPeople on Windows (https://invent.kde.org/frameworks/kpeople/-/merge_requests/7). Perhaps we should instead fully disable all DBus code in KPeople on Windows instead, given that the usefulness is questionable. Cheers Nico
Re: Notice of withdrawal of CI services: KDevelop and KDE Connect
Hi Ben, On 16.06.21 20:28, Ben Cooksley wrote: Hi all, The following is notice that I intend to withdraw CI services from the following two KDE projects due to faults in their code or build system which are having a significant adverse impact on the CI system and negatively impacting on other projects: - KDevelop - KDE Connect This withdrawal will be applied to all platforms. In the case of KDevelop, it has a series of unit tests which on FreeBSD cause gdb to hang and consume an entire CPU core indefinitely. This slows down builds for all other projects using that CI server, and also prevents KWin tests from proceeding - completely blocking it's jobs. This fault is in the debuggee_slow family of tests. As this issue has persisted for some time now despite being mentioned, I require that the family of tests in question be disabled across all platforms. In the case of KDE Connect, as part of it's configure process it runs an external command that results in dbus-daemon being launched. This process persists following the build and would only be cleaned up by our tooling that runs tests. Should the compilation fail (as it does currently) it will result in the CI builder being broken - which is why we have had so many Windows builds fail lately. As this is an issue that has occurred previously, I require that the configure time check which is launching dbus-daemon to be expunged from KDE Connect. As a reminder to all projects, running commands that interact with dbus-daemon or kdeinit is not permitted during configure or build time. Regards, Ben Cooksley KDE Sysadmin I think I know what causes the KDE Connect behavior. The CMake code calls 'ecm_find_qmlmodule(org.kde.people 1.0)', which results a call to 'qmlplugindump org.kde.kpeople 1.0' which causes parts of the KPeople code to be executed (PersonsModel in particular) which does some DBus things that then trigger dbus-daemon. As a stopgap solution to make the CI operational we can remove that ecm_find_qmlmodule call. In terms of a proper solution there was a recent effort to remove the mandatory DBus dependency from KPeople on Windows (https://invent.kde.org/frameworks/kpeople/-/merge_requests/7). Perhaps we should instead fully disable all DBus code in KPeople on Windows instead, given that the usefulness is questionable. Cheers Nico
Re: Notice of withdrawal of CI services: KDevelop and KDE Connect
How about if we add a config flag for our ci machines and configure cmake of these 2 project's test to ignore building/adding those problematic tests whenever it saw those flags? I don't know why but it doesn't sound correct to me to kill the ci build of any project because of these types of problems. Ömer Fadıl Usta PGP key : 0xfd11561976b1690b about.me/omerusta Ben Cooksley , 16 Haz 2021 Çar, 21:57 tarihinde şunu yazdı: > On Thu, Jun 17, 2021 at 6:41 AM Nate Graham wrote: > >> This kind of problem will be generically solved for everyone once we get >> GitLab's pre-commit CI, which can block merging of MRs until the >> failures are resolved--so they actually *will* be resolved. How soon can >> we get that finally rolled out across KDE? >> > > I'm afraid GitLab CI wouldn't have prevented this from occurring - because > the pre-merge CI still needs to run somewhere. > The problem here is that the simple act of running the build > degrades/breaks the builders for everyone else. > > In terms of a timeline on this, once I have the situation with Nextcloud > sorted out (which had to be prioritised as the version we're on goes out of > support in the next few months) we'll hopefully be able to work on GitLab > CI (assuming another vendor of ours doesn't go and pull another major > dependency bump stunt like Nextcloud did) > > >> Until that happens, this sort of problem will recur infinitely because >> people will continue to miss or ignore CI failures because they send >> emails after merge/commit rather than before, and are formatted >> semi-incomprehensibly. >> >> Nate >> > > Regards, > Ben > > >> >> >> On 6/16/21 12:28 PM, Ben Cooksley wrote: >> > Hi all, >> > >> > The following is notice that I intend to withdraw CI services from the >> > following two KDE projects due to faults in their code or build system >> > which are having a significant adverse impact on the CI system and >> > negatively impacting on other projects: >> > >> > - KDevelop >> > - KDE Connect >> > >> > This withdrawal will be applied to all platforms. >> > >> > In the case of KDevelop, it has a series of unit tests which on FreeBSD >> > cause gdb to hang and consume an entire CPU core indefinitely. This >> > slows down builds for all other projects using that CI server, and also >> > prevents KWin tests from proceeding - completely blocking it's jobs. >> > This fault is in the debuggee_slow family of tests. >> > >> > As this issue has persisted for some time now despite being mentioned, >> I >> > require that the family of tests in question be disabled across all >> > platforms. >> > >> > In the case of KDE Connect, as part of it's configure process it runs >> an >> > external command that results in dbus-daemon being launched. This >> > process persists following the build and would only be cleaned up by >> our >> > tooling that runs tests. Should the compilation fail (as it does >> > currently) it will result in the CI builder being broken - which is why >> > we have had so many Windows builds fail lately. >> > >> > As this is an issue that has occurred previously, I require that the >> > configure time check which is launching dbus-daemon to be expunged from >> > KDE Connect. >> > >> > As a reminder to all projects, running commands that interact with >> > dbus-daemon or kdeinit is not permitted during configure or build time. >> > >> > Regards, >> > Ben Cooksley >> > KDE Sysadmin >> >
Re: Notice of withdrawal of CI services: KDevelop and KDE Connect
On Thu, Jun 17, 2021 at 6:41 AM Nate Graham wrote: > This kind of problem will be generically solved for everyone once we get > GitLab's pre-commit CI, which can block merging of MRs until the > failures are resolved--so they actually *will* be resolved. How soon can > we get that finally rolled out across KDE? > I'm afraid GitLab CI wouldn't have prevented this from occurring - because the pre-merge CI still needs to run somewhere. The problem here is that the simple act of running the build degrades/breaks the builders for everyone else. In terms of a timeline on this, once I have the situation with Nextcloud sorted out (which had to be prioritised as the version we're on goes out of support in the next few months) we'll hopefully be able to work on GitLab CI (assuming another vendor of ours doesn't go and pull another major dependency bump stunt like Nextcloud did) > Until that happens, this sort of problem will recur infinitely because > people will continue to miss or ignore CI failures because they send > emails after merge/commit rather than before, and are formatted > semi-incomprehensibly. > > Nate > Regards, Ben > > > On 6/16/21 12:28 PM, Ben Cooksley wrote: > > Hi all, > > > > The following is notice that I intend to withdraw CI services from the > > following two KDE projects due to faults in their code or build system > > which are having a significant adverse impact on the CI system and > > negatively impacting on other projects: > > > > - KDevelop > > - KDE Connect > > > > This withdrawal will be applied to all platforms. > > > > In the case of KDevelop, it has a series of unit tests which on FreeBSD > > cause gdb to hang and consume an entire CPU core indefinitely. This > > slows down builds for all other projects using that CI server, and also > > prevents KWin tests from proceeding - completely blocking it's jobs. > > This fault is in the debuggee_slow family of tests. > > > > As this issue has persisted for some time now despite being mentioned, I > > require that the family of tests in question be disabled across all > > platforms. > > > > In the case of KDE Connect, as part of it's configure process it runs an > > external command that results in dbus-daemon being launched. This > > process persists following the build and would only be cleaned up by our > > tooling that runs tests. Should the compilation fail (as it does > > currently) it will result in the CI builder being broken - which is why > > we have had so many Windows builds fail lately. > > > > As this is an issue that has occurred previously, I require that the > > configure time check which is launching dbus-daemon to be expunged from > > KDE Connect. > > > > As a reminder to all projects, running commands that interact with > > dbus-daemon or kdeinit is not permitted during configure or build time. > > > > Regards, > > Ben Cooksley > > KDE Sysadmin >
Re: Notice of withdrawal of CI services: KDevelop and KDE Connect
On Thu, Jun 17, 2021 at 6:41 AM Nate Graham wrote: > This kind of problem will be generically solved for everyone once we get > GitLab's pre-commit CI, which can block merging of MRs until the > failures are resolved--so they actually *will* be resolved. How soon can > we get that finally rolled out across KDE? > I'm afraid GitLab CI wouldn't have prevented this from occurring - because the pre-merge CI still needs to run somewhere. The problem here is that the simple act of running the build degrades/breaks the builders for everyone else. In terms of a timeline on this, once I have the situation with Nextcloud sorted out (which had to be prioritised as the version we're on goes out of support in the next few months) we'll hopefully be able to work on GitLab CI (assuming another vendor of ours doesn't go and pull another major dependency bump stunt like Nextcloud did) > Until that happens, this sort of problem will recur infinitely because > people will continue to miss or ignore CI failures because they send > emails after merge/commit rather than before, and are formatted > semi-incomprehensibly. > > Nate > Regards, Ben > > > On 6/16/21 12:28 PM, Ben Cooksley wrote: > > Hi all, > > > > The following is notice that I intend to withdraw CI services from the > > following two KDE projects due to faults in their code or build system > > which are having a significant adverse impact on the CI system and > > negatively impacting on other projects: > > > > - KDevelop > > - KDE Connect > > > > This withdrawal will be applied to all platforms. > > > > In the case of KDevelop, it has a series of unit tests which on FreeBSD > > cause gdb to hang and consume an entire CPU core indefinitely. This > > slows down builds for all other projects using that CI server, and also > > prevents KWin tests from proceeding - completely blocking it's jobs. > > This fault is in the debuggee_slow family of tests. > > > > As this issue has persisted for some time now despite being mentioned, I > > require that the family of tests in question be disabled across all > > platforms. > > > > In the case of KDE Connect, as part of it's configure process it runs an > > external command that results in dbus-daemon being launched. This > > process persists following the build and would only be cleaned up by our > > tooling that runs tests. Should the compilation fail (as it does > > currently) it will result in the CI builder being broken - which is why > > we have had so many Windows builds fail lately. > > > > As this is an issue that has occurred previously, I require that the > > configure time check which is launching dbus-daemon to be expunged from > > KDE Connect. > > > > As a reminder to all projects, running commands that interact with > > dbus-daemon or kdeinit is not permitted during configure or build time. > > > > Regards, > > Ben Cooksley > > KDE Sysadmin >
Re: Notice of withdrawal of CI services: KDevelop and KDE Connect
This kind of problem will be generically solved for everyone once we get GitLab's pre-commit CI, which can block merging of MRs until the failures are resolved--so they actually *will* be resolved. How soon can we get that finally rolled out across KDE? Until that happens, this sort of problem will recur infinitely because people will continue to miss or ignore CI failures because they send emails after merge/commit rather than before, and are formatted semi-incomprehensibly. Nate On 6/16/21 12:28 PM, Ben Cooksley wrote: Hi all, The following is notice that I intend to withdraw CI services from the following two KDE projects due to faults in their code or build system which are having a significant adverse impact on the CI system and negatively impacting on other projects: - KDevelop - KDE Connect This withdrawal will be applied to all platforms. In the case of KDevelop, it has a series of unit tests which on FreeBSD cause gdb to hang and consume an entire CPU core indefinitely. This slows down builds for all other projects using that CI server, and also prevents KWin tests from proceeding - completely blocking it's jobs. This fault is in the debuggee_slow family of tests. As this issue has persisted for some time now despite being mentioned, I require that the family of tests in question be disabled across all platforms. In the case of KDE Connect, as part of it's configure process it runs an external command that results in dbus-daemon being launched. This process persists following the build and would only be cleaned up by our tooling that runs tests. Should the compilation fail (as it does currently) it will result in the CI builder being broken - which is why we have had so many Windows builds fail lately. As this is an issue that has occurred previously, I require that the configure time check which is launching dbus-daemon to be expunged from KDE Connect. As a reminder to all projects, running commands that interact with dbus-daemon or kdeinit is not permitted during configure or build time. Regards, Ben Cooksley KDE Sysadmin
Notice of withdrawal of CI services: KDevelop and KDE Connect
Hi all, The following is notice that I intend to withdraw CI services from the following two KDE projects due to faults in their code or build system which are having a significant adverse impact on the CI system and negatively impacting on other projects: - KDevelop - KDE Connect This withdrawal will be applied to all platforms. In the case of KDevelop, it has a series of unit tests which on FreeBSD cause gdb to hang and consume an entire CPU core indefinitely. This slows down builds for all other projects using that CI server, and also prevents KWin tests from proceeding - completely blocking it's jobs. This fault is in the debuggee_slow family of tests. As this issue has persisted for some time now despite being mentioned, I require that the family of tests in question be disabled across all platforms. In the case of KDE Connect, as part of it's configure process it runs an external command that results in dbus-daemon being launched. This process persists following the build and would only be cleaned up by our tooling that runs tests. Should the compilation fail (as it does currently) it will result in the CI builder being broken - which is why we have had so many Windows builds fail lately. As this is an issue that has occurred previously, I require that the configure time check which is launching dbus-daemon to be expunged from KDE Connect. As a reminder to all projects, running commands that interact with dbus-daemon or kdeinit is not permitted during configure or build time. Regards, Ben Cooksley KDE Sysadmin
Notice of withdrawal of CI services: KDevelop and KDE Connect
Hi all, The following is notice that I intend to withdraw CI services from the following two KDE projects due to faults in their code or build system which are having a significant adverse impact on the CI system and negatively impacting on other projects: - KDevelop - KDE Connect This withdrawal will be applied to all platforms. In the case of KDevelop, it has a series of unit tests which on FreeBSD cause gdb to hang and consume an entire CPU core indefinitely. This slows down builds for all other projects using that CI server, and also prevents KWin tests from proceeding - completely blocking it's jobs. This fault is in the debuggee_slow family of tests. As this issue has persisted for some time now despite being mentioned, I require that the family of tests in question be disabled across all platforms. In the case of KDE Connect, as part of it's configure process it runs an external command that results in dbus-daemon being launched. This process persists following the build and would only be cleaned up by our tooling that runs tests. Should the compilation fail (as it does currently) it will result in the CI builder being broken - which is why we have had so many Windows builds fail lately. As this is an issue that has occurred previously, I require that the configure time check which is launching dbus-daemon to be expunged from KDE Connect. As a reminder to all projects, running commands that interact with dbus-daemon or kdeinit is not permitted during configure or build time. Regards, Ben Cooksley KDE Sysadmin
KDE CI: Frameworks » syntax-highlighting » kf5-qt5 WindowsMSVCQt5.15 - Build # 206 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/syntax-highlighting/job/kf5-qt5%20WindowsMSVCQt5.15/206/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 16 Jun 2021 18:08:22 + Build duration: 3 min 44 sec and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)
KDE CI: Frameworks » breeze-icons » kf5-qt5 WindowsMSVCQt5.15 - Build # 129 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/breeze-icons/job/kf5-qt5%20WindowsMSVCQt5.15/129/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 16 Jun 2021 18:08:24 + Build duration: 2 min 5 sec and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s)
KDE CI: Frameworks » syntax-highlighting » kf5-qt5 WindowsMSVCQt5.15 - Build # 205 - Still Failing!
BUILD FAILURE
Build URL
https://build.kde.org/job/Frameworks/job/syntax-highlighting/job/kf5-qt5%20WindowsMSVCQt5.15/205/
Project:
kf5-qt5 WindowsMSVCQt5.15
Date of build:
Wed, 16 Jun 2021 17:58:14 +
Build duration:
0.34 sec and counting
CONSOLE OUTPUT
Started by an SCM changeRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Windows Builder Iota in C:\CI\workspace\Frameworks\syntax-highlighting\kf5-qt5 WindowsMSVCQt5.15[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] ws[2021-06-16T17:58:14.680Z] Running in C:/CI/Job Build[Pipeline] {[Pipeline] catchError[Pipeline] {[Pipeline] stage[Pipeline] { (Checkout Sources)[Pipeline] deleteDir[Pipeline] }[Pipeline] // stage[Pipeline] }[2021-06-16T17:58:14.920Z] Also: Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T17:58:14.920Z] [2021-06-16T17:58:14.920Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T17:58:14.920Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:58:14.920Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:58:14.920Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:58:14.920Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:58:14.920Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:58:14.920Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T17:58:14.920Z] Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T17:58:14.920Z] [2021-06-16T17:58:14.920Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T17:58:14.920Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:58:14.920Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:58:14.920Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:58:14.920Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:58:14.920Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:58:14.920Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T17:58:14.920Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build\build with directory contents: [][2021-06-16T17:58:14.920Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T17:58:14.920Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T17:58:14.920Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T17:58:14.920Z] at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)[2021-06-16T17:58:14.920Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)[2021-06-16T17:58:14.920Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T17:58:14.920Z] Also: Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T17:58:14.920Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:58:14.920Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:58:14.920Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:58:14.920Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T17:58:14.920Z] Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T17:58:14.920Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:58:14.920Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:58:14.920Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:58:14.920Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T17:58:14.920Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build with directory contents: [C:\CI\Job Build\build][2021-06-16T17:58:14.920Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T17:58:14.920Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T17:58:14.920Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T17:58:14.920Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T17:58:14.920Z] Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect
KDE CI: Frameworks » syntax-highlighting » kf5-qt5 WindowsMSVCQt5.15 - Build # 204 - Failure!
BUILD FAILURE
Build URL
https://build.kde.org/job/Frameworks/job/syntax-highlighting/job/kf5-qt5%20WindowsMSVCQt5.15/204/
Project:
kf5-qt5 WindowsMSVCQt5.15
Date of build:
Wed, 16 Jun 2021 17:58:04 +
Build duration:
0.44 sec and counting
CONSOLE OUTPUT
Started by an SCM changeRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Windows Builder Iota in C:\CI\workspace\Frameworks\syntax-highlighting\kf5-qt5 WindowsMSVCQt5.15[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] ws[2021-06-16T17:58:04.868Z] Running in C:/CI/Job Build[Pipeline] {[Pipeline] catchError[Pipeline] {[Pipeline] stage[Pipeline] { (Checkout Sources)[Pipeline] deleteDir[Pipeline] }[Pipeline] // stage[Pipeline] }[2021-06-16T17:58:05.105Z] Also: Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T17:58:05.105Z] [2021-06-16T17:58:05.105Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T17:58:05.105Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:58:05.105Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:58:05.105Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:58:05.105Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:58:05.105Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:58:05.105Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T17:58:05.105Z] Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T17:58:05.105Z] [2021-06-16T17:58:05.105Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T17:58:05.105Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:58:05.105Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:58:05.105Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:58:05.105Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:58:05.105Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:58:05.105Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T17:58:05.105Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build\build with directory contents: [][2021-06-16T17:58:05.105Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T17:58:05.105Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T17:58:05.105Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T17:58:05.105Z] at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)[2021-06-16T17:58:05.105Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)[2021-06-16T17:58:05.105Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T17:58:05.105Z] Also: Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T17:58:05.105Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:58:05.105Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:58:05.105Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:58:05.105Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T17:58:05.105Z] Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T17:58:05.105Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:58:05.105Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:58:05.105Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:58:05.105Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T17:58:05.105Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build with directory contents: [C:\CI\Job Build\build][2021-06-16T17:58:05.105Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T17:58:05.105Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T17:58:05.105Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T17:58:05.105Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T17:58:05.105Z] Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect
KDE CI: Frameworks » extra-cmake-modules » kf5-qt5 WindowsMSVCQt5.15 - Build # 153 - Still Failing!
BUILD FAILURE
Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20WindowsMSVCQt5.15/153/
Project:
kf5-qt5 WindowsMSVCQt5.15
Date of build:
Wed, 16 Jun 2021 17:17:17 +
Build duration:
0.41 sec and counting
CONSOLE OUTPUT
Started by an SCM changeRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Windows Builder Iota in C:\CI\workspace\Frameworks\extra-cmake-modules\kf5-qt5 WindowsMSVCQt5.15[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] ws[2021-06-16T17:17:18.167Z] Running in C:/CI/Job Build[Pipeline] {[Pipeline] catchError[Pipeline] {[Pipeline] stage[Pipeline] { (Checkout Sources)[Pipeline] deleteDir[Pipeline] }[Pipeline] // stage[Pipeline] }[2021-06-16T17:17:18.417Z] Also: Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T17:17:18.417Z] [2021-06-16T17:17:18.417Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T17:17:18.417Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:17:18.417Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:17:18.417Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:17:18.417Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:17:18.417Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:17:18.418Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T17:17:18.418Z] Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T17:17:18.418Z] [2021-06-16T17:17:18.418Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T17:17:18.418Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:17:18.418Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:17:18.418Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:17:18.418Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:17:18.418Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:17:18.418Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T17:17:18.418Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build\build with directory contents: [][2021-06-16T17:17:18.418Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T17:17:18.418Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T17:17:18.418Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T17:17:18.418Z] at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)[2021-06-16T17:17:18.418Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)[2021-06-16T17:17:18.418Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T17:17:18.418Z] Also: Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T17:17:18.418Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:17:18.418Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:17:18.418Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:17:18.418Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T17:17:18.418Z] Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T17:17:18.418Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:17:18.418Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:17:18.418Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:17:18.418Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T17:17:18.418Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build with directory contents: [C:\CI\Job Build\build][2021-06-16T17:17:18.418Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T17:17:18.418Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T17:17:18.418Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T17:17:18.418Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T17:17:18.418Z] Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect
KDE CI: Frameworks » extra-cmake-modules » kf5-qt5 WindowsMSVCQt5.15 - Build # 152 - Failure!
BUILD FAILURE
Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20WindowsMSVCQt5.15/152/
Project:
kf5-qt5 WindowsMSVCQt5.15
Date of build:
Wed, 16 Jun 2021 17:17:07 +
Build duration:
0.51 sec and counting
CONSOLE OUTPUT
Started by an SCM changeRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Windows Builder Iota in C:\CI\workspace\Frameworks\extra-cmake-modules\kf5-qt5 WindowsMSVCQt5.15[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] ws[2021-06-16T17:17:08.341Z] Running in C:/CI/Job Build[Pipeline] {[Pipeline] catchError[Pipeline] {[Pipeline] stage[Pipeline] { (Checkout Sources)[Pipeline] deleteDir[Pipeline] }[Pipeline] // stage[Pipeline] }[2021-06-16T17:17:08.695Z] Also: Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T17:17:08.695Z] [2021-06-16T17:17:08.695Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T17:17:08.695Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:17:08.695Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:17:08.695Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:17:08.695Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:17:08.695Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:17:08.695Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T17:17:08.695Z] Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T17:17:08.695Z] [2021-06-16T17:17:08.695Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T17:17:08.695Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:17:08.695Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T17:17:08.695Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:17:08.695Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:17:08.695Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:17:08.695Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T17:17:08.695Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build\build with directory contents: [][2021-06-16T17:17:08.695Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T17:17:08.695Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T17:17:08.695Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T17:17:08.695Z] at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)[2021-06-16T17:17:08.695Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)[2021-06-16T17:17:08.695Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T17:17:08.695Z] Also: Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T17:17:08.695Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:17:08.695Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:17:08.695Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:17:08.695Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T17:17:08.695Z] Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T17:17:08.695Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T17:17:08.695Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T17:17:08.695Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T17:17:08.695Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T17:17:08.695Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build with directory contents: [C:\CI\Job Build\build][2021-06-16T17:17:08.695Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T17:17:08.695Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T17:17:08.695Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T17:17:08.695Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T17:17:08.695Z] Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect
KDE CI: Frameworks » breeze-icons » kf5-qt5 WindowsMSVCQt5.15 - Build # 128 - Still Failing!
BUILD FAILURE
Build URL
https://build.kde.org/job/Frameworks/job/breeze-icons/job/kf5-qt5%20WindowsMSVCQt5.15/128/
Project:
kf5-qt5 WindowsMSVCQt5.15
Date of build:
Wed, 16 Jun 2021 16:43:27 +
Build duration:
0.31 sec and counting
CONSOLE OUTPUT
Started by an SCM changeRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Windows Builder Iota in C:\CI\workspace\Frameworks\breeze-icons\kf5-qt5 WindowsMSVCQt5.15[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] ws[2021-06-16T16:43:27.867Z] Running in C:/CI/Job Build[Pipeline] {[Pipeline] catchError[Pipeline] {[Pipeline] stage[Pipeline] { (Checkout Sources)[Pipeline] deleteDir[Pipeline] }[Pipeline] // stage[Pipeline] }[2021-06-16T16:43:28.120Z] Also: Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T16:43:28.120Z] [2021-06-16T16:43:28.120Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T16:43:28.120Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T16:43:28.120Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T16:43:28.120Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T16:43:28.120Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T16:43:28.120Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T16:43:28.120Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T16:43:28.120Z] Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T16:43:28.120Z] [2021-06-16T16:43:28.120Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T16:43:28.120Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T16:43:28.120Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T16:43:28.120Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T16:43:28.120Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T16:43:28.120Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T16:43:28.120Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T16:43:28.120Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build\build with directory contents: [][2021-06-16T16:43:28.120Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T16:43:28.120Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T16:43:28.120Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T16:43:28.120Z] at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)[2021-06-16T16:43:28.120Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)[2021-06-16T16:43:28.120Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T16:43:28.120Z] Also: Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T16:43:28.120Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T16:43:28.120Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T16:43:28.120Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T16:43:28.120Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T16:43:28.120Z] Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T16:43:28.120Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T16:43:28.120Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T16:43:28.120Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T16:43:28.120Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T16:43:28.120Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build with directory contents: [C:\CI\Job Build\build][2021-06-16T16:43:28.120Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T16:43:28.120Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T16:43:28.120Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T16:43:28.120Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T16:43:28.120Z] Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from
KDE CI: Frameworks » breeze-icons » kf5-qt5 WindowsMSVCQt5.15 - Build # 127 - Failure!
BUILD FAILURE
Build URL
https://build.kde.org/job/Frameworks/job/breeze-icons/job/kf5-qt5%20WindowsMSVCQt5.15/127/
Project:
kf5-qt5 WindowsMSVCQt5.15
Date of build:
Wed, 16 Jun 2021 16:43:17 +
Build duration:
0.4 sec and counting
CONSOLE OUTPUT
Started by an SCM changeRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Windows Builder Iota in C:\CI\workspace\Frameworks\breeze-icons\kf5-qt5 WindowsMSVCQt5.15[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] ws[2021-06-16T16:43:17.997Z] Running in C:/CI/Job Build[Pipeline] {[Pipeline] catchError[Pipeline] {[Pipeline] stage[Pipeline] { (Checkout Sources)[Pipeline] deleteDir[Pipeline] }[Pipeline] // stage[Pipeline] }[2021-06-16T16:43:18.241Z] Also: Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T16:43:18.241Z] [2021-06-16T16:43:18.241Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T16:43:18.241Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T16:43:18.241Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T16:43:18.241Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T16:43:18.241Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T16:43:18.241Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T16:43:18.241Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T16:43:18.241Z] Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T16:43:18.241Z] [2021-06-16T16:43:18.241Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T16:43:18.241Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T16:43:18.241Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T16:43:18.241Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T16:43:18.241Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T16:43:18.241Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T16:43:18.241Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T16:43:18.241Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build\build with directory contents: [][2021-06-16T16:43:18.241Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T16:43:18.241Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T16:43:18.241Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T16:43:18.241Z] at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)[2021-06-16T16:43:18.241Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)[2021-06-16T16:43:18.241Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T16:43:18.241Z] Also: Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T16:43:18.241Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T16:43:18.241Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T16:43:18.241Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T16:43:18.241Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T16:43:18.241Z] Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T16:43:18.241Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T16:43:18.241Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T16:43:18.241Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T16:43:18.241Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T16:43:18.241Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build with directory contents: [C:\CI\Job Build\build][2021-06-16T16:43:18.241Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T16:43:18.242Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T16:43:18.242Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T16:43:18.242Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T16:43:18.242Z] Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from
Re: AudioTube in KDEReview
Hola
On 16.06.21 00:44, Jonah Brüchert wrote:
> I would like to move AudioTube to KDEReview.
- the source is almost reuse compliant but not quite. needs some extra
data files equipped with CC-0 or the like [1][2]. You could then also
add an include on
https://invent.kde.org/sysadmin/ci-tooling/raw/master/invent/ci-reuse.yml
to your gitlab-ci.yml to ensure it stays at complete coverage
- l10n is not correctly set up. You need to set a translation domain on
the KLocalizedContext
- app crashes when ytmusicapi isn't installed ;) maybe add a
find_package that simply tries to run a simple script importing it? tag
the package RUNTIME. that way the runtime dep is properly codified
- same for youtube_dl which seems to be required behind the scenes
- app isn't kcrash enabled :((
- seeking doesn't seem to do anything. I get `audiotube(103398)/(qml)
onMoved: Value: 71454.30987821381` as output but then the seek doesn't
actually happen
- something is also wonky with the playlist. it doesn't cover the width
(when data fails to load). it is overlapped by the scrollbar. clear and
shuffle don't seem to have labels though there would be enough space
https://i.imgur.com/Q3IoaBj.png
- on some artists I get `TypeError: 'NoneType' object is not iterable `
https://i.imgur.com/U8BKHbQ.png
- on the subject of errors. I'm not sure the passive popup overlapping
the controls at the bottom is all that nice
- appdata should probably describe the
- ytmusic.cpp forces LC_ALL to en_us, that seems a bit fishy and it
doesn't explain why either
- VideoInfoExtractor ctor should be explicit
- PlaylistUtils looks like it maybe should be a namespace not a class.
feel free to ignore me if you disagree
- in asyncytmusic.h there's a typo in 'ininitalized'
- ~YTMusicThread be tagged `override`
- example has a type in 'excaustive'
- you may want to do a pass over all strings. I'm seeing some action
strings not using title capitalization (e.g. i18n("Add to playlist")
i18n("Play next")) [3]
[1] https://apachelog.wordpress.com/2021/04/06/reuse-licensing-helper/
[2]
https://community.kde.org/Guidelines_and_HOWTOs/Licensing#License_Statements_in_Non-Source-Code_Files
[3] https://develop.kde.org/hig/style/writing/capitalization/
KDE CI: Frameworks » ktexteditor » kf5-qt5 WindowsMSVCQt5.15 - Build # 311 - Still unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/ktexteditor/job/kf5-qt5%20WindowsMSVCQt5.15/311/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 16 Jun 2021 09:41:09 + Build duration: 45 min and counting JUnit Tests Name: projectroot Failed: 9 test(s), Passed: 55 test(s), Skipped: 0 test(s), Total: 64 test(s)Failed: projectroot.autotests.inlinenote_testFailed: projectroot.autotests.katedocument_testFailed: projectroot.autotests.kateindenttest_testCppstyleFailed: projectroot.autotests.kateindenttest_testCstyleFailed: projectroot.autotests.kateindenttest_testRubyFailed: projectroot.autotests.katetextbuffertestFailed: projectroot.autotests.kateview_testFailed: projectroot.autotests.messagetestFailed: projectroot.autotests.movingrange_testName: projectroot.autotests.src Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s)
KDE CI: Frameworks » krunner » kf5-qt5 WindowsMSVCQt5.15 - Build # 132 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/krunner/job/kf5-qt5%20WindowsMSVCQt5.15/132/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 16 Jun 2021 09:49:03 + Build duration: 34 min and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s)
KDE CI: Frameworks » syntax-highlighting » kf5-qt5 WindowsMSVCQt5.15 - Build # 203 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/syntax-highlighting/job/kf5-qt5%20WindowsMSVCQt5.15/203/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 16 Jun 2021 09:41:22 + Build duration: 39 min and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)
KDE CI: Frameworks » plasma-framework » kf5-qt5 WindowsMSVCQt5.15 - Build # 336 - Still unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/plasma-framework/job/kf5-qt5%20WindowsMSVCQt5.15/336/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 16 Jun 2021 09:41:11 + Build duration: 37 min and counting JUnit Tests Name: projectroot Failed: 4 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 9 test(s)Failed: projectroot.autotests.coronatestFailed: projectroot.autotests.plasma_dialogstatetestFailed: projectroot.autotests.plasma_iconitemtestFailed: projectroot.autotests.plasma_themetest
KDE CI: Frameworks » kwallet » kf5-qt5 WindowsMSVCQt5.15 - Build # 75 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kwallet/job/kf5-qt5%20WindowsMSVCQt5.15/75/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 16 Jun 2021 09:41:08 + Build duration: 34 min and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
Re: KDE's Official Standlaone application packages are missing translations for some basic buttons
Tyson Tan ha scritto: > Hi team, > > I wrote this email to discuss a KDE internationalization issue: KDE's Official > Standlaone application packages (Windows/macOS/appimage) have been missing > translations for some basic buttons: > > Krita: > https://www.tysontan.com/temp/free_software/kde_bugs/krita2.png > > digiKam: > https://www.tysontan.com/temp/free_software/kde_bugs/digikam2.png > > Kdenlive: > https://www.tysontan.com/temp/free_software/kde_bugs/kdenlive.png > > Kate: > https://www.tysontan.com/temp/free_software/kde_bugs/kate.png > > Generally speaking: > 1) It only affects DIALOGUES' basic buttons like "OK", "Cancel", "Help" and so > on. > 2) It affects all languages. > 3) It happens only on KDE's official, standalone builds. Packages provided by > Linux distros are unaffected. I've checked the Kate appdata and the Kate win64 binaries from binary-factory and they don't include the Qt translations (they ships all the other translations). So maybe just a configuration issue on the CI? -- Luigi
KDE CI: Frameworks » breeze-icons » kf5-qt5 WindowsMSVCQt5.15 - Build # 126 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/breeze-icons/job/kf5-qt5%20WindowsMSVCQt5.15/126/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 16 Jun 2021 09:40:33 + Build duration: 6 min 7 sec and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s)
KDE CI: Frameworks » kcmutils » kf5-qt5 WindowsMSVCQt5.15 - Build # 93 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kcmutils/job/kf5-qt5%20WindowsMSVCQt5.15/93/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 16 Jun 2021 09:40:32 + Build duration: 5 min 39 sec and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.autotests Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
KDE CI: Frameworks » attica » kf5-qt5 WindowsMSVCQt5.15 - Build # 54 - Still unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/attica/job/kf5-qt5%20WindowsMSVCQt5.15/54/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 16 Jun 2021 09:40:34 + Build duration: 4 min 19 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 3 test(s)Failed: projectroot.autotests.providertest
KDE CI: Frameworks » kdeclarative » kf5-qt5 WindowsMSVCQt5.15 - Build # 96 - Still unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kdeclarative/job/kf5-qt5%20WindowsMSVCQt5.15/96/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 16 Jun 2021 09:40:31 + Build duration: 2 min 27 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.quickviewsharedengine
KDE's Official Standlaone application packages are missing translations for some basic buttons
Hi team, I wrote this email to discuss a KDE internationalization issue: KDE's Official Standlaone application packages (Windows/macOS/appimage) have been missing translations for some basic buttons: Krita: https://www.tysontan.com/temp/free_software/kde_bugs/krita2.png digiKam: https://www.tysontan.com/temp/free_software/kde_bugs/digikam2.png Kdenlive: https://www.tysontan.com/temp/free_software/kde_bugs/kdenlive.png Kate: https://www.tysontan.com/temp/free_software/kde_bugs/kate.png Generally speaking: 1) It only affects DIALOGUES' basic buttons like "OK", "Cancel", "Help" and so on. 2) It affects all languages. 3) It happens only on KDE's official, standalone builds. Packages provided by Linux distros are unaffected. 4) This is not a new issue. It has been this way since ever I know KDE. It seems KDE application must use strings from Qttranslation to make some basic buttons translated. In an attempt to fix this issue, Krita team tried to add "OK", "Cancel" to krita.pot, but to no avail. Recently the Krita team seemed to have solved the problem with some hacks: Bug report and relative findings: https://bugs.kde.org/show_bug.cgi?id=395338#c68 Git Commit: https://invent.kde.org/graphics/krita/commit/6ddad6502f3742c08ca89c3d1db36f331cf95e55 But since this issue is complicated and affects all KDE's official packages, please allow me to bring it to your attention, and hopefully fixing it on a lower level, so each project doesn't have to apply their own hacks in the future. Best regards, Tyson Tan
KDE CI: Frameworks » ktexteditor » kf5-qt5 WindowsMSVCQt5.15 - Build # 310 - Still Failing!
BUILD FAILURE
Build URL
https://build.kde.org/job/Frameworks/job/ktexteditor/job/kf5-qt5%20WindowsMSVCQt5.15/310/
Project:
kf5-qt5 WindowsMSVCQt5.15
Date of build:
Wed, 16 Jun 2021 08:51:19 +
Build duration:
4.3 sec and counting
CONSOLE OUTPUT
Started by an SCM changeRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Windows Builder Iota in C:\CI\workspace\Frameworks\ktexteditor\kf5-qt5 WindowsMSVCQt5.15[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] ws[2021-06-16T08:51:19.486Z] Running in C:/CI/Job Build[Pipeline] {[Pipeline] catchError[Pipeline] {[Pipeline] stage[Pipeline] { (Checkout Sources)[Pipeline] deleteDir[Pipeline] }[Pipeline] // stage[Pipeline] }[2021-06-16T08:51:23.730Z] Also: Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T08:51:23.730Z] [2021-06-16T08:51:23.730Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T08:51:23.730Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T08:51:23.730Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T08:51:23.730Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T08:51:23.730Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T08:51:23.730Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T08:51:23.730Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T08:51:23.730Z] Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T08:51:23.730Z] [2021-06-16T08:51:23.730Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T08:51:23.730Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T08:51:23.730Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T08:51:23.730Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T08:51:23.730Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T08:51:23.730Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T08:51:23.730Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T08:51:23.730Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build\build with directory contents: [][2021-06-16T08:51:23.730Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T08:51:23.730Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T08:51:23.730Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T08:51:23.730Z] at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)[2021-06-16T08:51:23.730Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)[2021-06-16T08:51:23.730Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T08:51:23.730Z] Also: Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T08:51:23.730Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T08:51:23.730Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T08:51:23.730Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T08:51:23.730Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T08:51:23.730Z] Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T08:51:23.730Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T08:51:23.730Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T08:51:23.730Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T08:51:23.730Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T08:51:23.730Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build with directory contents: [C:\CI\Job Build\build][2021-06-16T08:51:23.730Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T08:51:23.730Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T08:51:23.730Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T08:51:23.730Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T08:51:23.730Z] Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from
KDE CI: Frameworks » ktexteditor » kf5-qt5 WindowsMSVCQt5.15 - Build # 309 - Failure!
BUILD FAILURE
Build URL
https://build.kde.org/job/Frameworks/job/ktexteditor/job/kf5-qt5%20WindowsMSVCQt5.15/309/
Project:
kf5-qt5 WindowsMSVCQt5.15
Date of build:
Wed, 16 Jun 2021 08:51:04 +
Build duration:
4.6 sec and counting
CONSOLE OUTPUT
Started by an SCM changeRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Windows Builder Iota in C:\CI\workspace\Frameworks\ktexteditor\kf5-qt5 WindowsMSVCQt5.15[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] ws[2021-06-16T08:51:05.087Z] Running in C:/CI/Job Build[Pipeline] {[Pipeline] catchError[Pipeline] {[Pipeline] stage[Pipeline] { (Checkout Sources)[Pipeline] deleteDir[Pipeline] }[Pipeline] // stage[Pipeline] }[2021-06-16T08:51:09.546Z] Also: Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T08:51:09.546Z] [2021-06-16T08:51:09.546Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T08:51:09.546Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T08:51:09.546Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T08:51:09.546Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T08:51:09.546Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T08:51:09.546Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T08:51:09.546Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T08:51:09.546Z] Also: java.nio.file.FileSystemException: C:\CI\Job Build\build: The process cannot access the file because it is being used by another process.[2021-06-16T08:51:09.546Z] [2021-06-16T08:51:09.546Z] at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)[2021-06-16T08:51:09.546Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T08:51:09.546Z] at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)[2021-06-16T08:51:09.546Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T08:51:09.546Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T08:51:09.546Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T08:51:09.546Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T08:51:09.546Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build\build with directory contents: [][2021-06-16T08:51:09.546Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T08:51:09.546Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T08:51:09.546Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T08:51:09.546Z] at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)[2021-06-16T08:51:09.546Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)[2021-06-16T08:51:09.546Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T08:51:09.546Z] Also: Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T08:51:09.546Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T08:51:09.546Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T08:51:09.546Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T08:51:09.546Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)[2021-06-16T08:51:09.546Z] Also: java.nio.file.DirectoryNotEmptyException: C:\CI\Job Build[2021-06-16T08:51:09.546Z] at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)[2021-06-16T08:51:09.546Z] at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)[2021-06-16T08:51:09.546Z] at java.nio.file.Files.deleteIfExists(Unknown Source)[2021-06-16T08:51:09.546Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)[2021-06-16T08:51:09.546Z] jenkins.util.io.CompositeIOException: Unable to remove directory C:\CI\Job Build with directory contents: [C:\CI\Job Build\build][2021-06-16T08:51:09.546Z] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:250)[2021-06-16T08:51:09.546Z] at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)[2021-06-16T08:51:09.546Z] at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)[2021-06-16T08:51:09.546Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)[2021-06-16T08:51:09.546Z] Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from
