From kde-frameworks-devel Thu Jun 17 09:36:40 2021 From: Ben Cooksley Date: Thu, 17 Jun 2021 09:36:40 +0000 To: kde-frameworks-devel Subject: Re: Notice of withdrawal of CI services: KDevelop and KDE Connect Message-Id: X-MARC-Message: https://marc.info/?l=kde-frameworks-devel&m=162392263814508 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--0000000000007f67cf05c4f2f28a" --0000000000007f67cf05c4f2f28a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jun 17, 2021 at 7:26 AM Avamander wrote: > Hi, > Hi there, > > 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, w= hy > 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 =F0= =9F=A4=AA > According to my email archives we've not previously corresponded - and the name "Avamander" is certainly new to me. The five lists in question were chosen deliberately for the following reasons: 1) kdeconnect@kde.org as the matter related to KDE Connect 2) kdevelop-devel@kde.org as the matter related to KDevelop 3) kde-frameworks-devel@kde.org as the email explained why Frameworks had experienced a substantial number of Windows CI failures lately 4) kde-devel@kde.org as the email explained to various Extragear projects why they had experienced Windows CI failures as well 5) sysadmin@kde.org as the matter related to our infrastructure > On a very related topic, for the third time, send the kdeconnect CI statu= s > emails to the actual developers and contributors for whom they are > actionable, not the entire kdeconnect mailing list. It's just noise for t= he > majority of non-code contributors, non-code contributors that might be ab= le > to help with support questions but who are very likely ignoring the list > due to horrifically bad SNR. > Please direct your complaints regarding the content and moderation of the kdeconnect@kde.org to the list administrators - kdeconnect-owner@kde.org - in the first instance or raise a thread on that mailing list. With regards to the CI status emails, these were setup at the request of the KDE Connect developers in https://phabricator.kde.org/D13794 > > > Have an extra day, > Avamander > Regards, Ben > > 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 slow= s >> down builds for all other projects using that CI server, and also preven= ts >> KWin tests from proceeding - completely blocking it's jobs. This fault i= s >> 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 proces= s >> 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 w= ill >> 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 >> > --0000000000007f67cf05c4f2f28a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Jun 17, 2021 at 7:26 AM Avamander= <avamander@gmail.com> wro= te:
Hi,

Hi there,
=C2=A0

This is indeed an issue tha= t has=C2=A0occurred=C2=A0previously,=C2=A0and actually I've=C2=A0writte= n to you,=C2=A0Ben, once before about this. Now I'm asking again, why i= s it necessary to email FIVE mailing lists for issues that are prima= rily solved by a much much smaller subgroup of people? Maybe send it to a f= ew C++ lists as well, maybe someone'll jump out and fix the CI=C2=A0=F0= =9F=A4=AA

According to my e= mail archives we've not previously corresponded - and the name "Av= amander" is certainly new to me.=C2=A0

The fi= ve lists in question were chosen deliberately for the following reasons:
1) kdeconnect@kde.org as = the matter related to KDE Connect
2) kdevelop-devel@kde.org as the matter related to KDevelop<= /div>
3) kde-frameworks= -devel@kde.org as the email explained why Frameworks had experienced a = substantial number of Windows CI failures lately
4) kde-devel@kde.org as the email explained to var= ious Extragear projects why they had experienced Windows CI failures as wel= l
5) sysadmin@kde.org as = the matter related to our infrastructure


On= a very related topic, for the third time, send the kdeconnect CI status em= ails to the actual developers and contributors for whom they are actionable= , not the entire kdeconnect mailing list. It's just noise for the major= ity of non-code contributors, non-code contributors that might be able to h= elp with support questions but who are very likely ignoring the list due to= horrifically bad SNR.

Plea= se direct your complaints regarding the content and moderation of the kdeconnect@kde.org to the list adminis= trators - kdeconnect-owner@kde.= org - in the first instance or raise a thread on that mailing list. Wit= h regards to the CI status emails, these were setup at the request of the K= DE Connect developers in=C2=A0https://phabricator.kde.org/D13794




Have an extra day,
Avamand= er

Regards,
Ben
=
=C2=A0

On Wed, Jun 16= , 2021 at 9:29 PM Ben Cooksley <bcooksley@kde.org> wrote:
Hi all,

The following is notice that I intend to withdraw CI services from the fo= llowing 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 imp= acting on other projects:

- KDevelop
- K= DE Connect

This withdrawal will be applied to all = platforms.

In the case of KDevelop, it has a serie= s of unit tests which on FreeBSD cause gdb to hang and consume an entire CP= U core indefinitely. This slows down builds for all other projects using th= at CI server, and also prevents KWin tests from proceeding - completely blo= cking it's jobs. This fault is in the debuggee_slow family of tests.

As this issue has persisted for some time now despit= e being mentioned, I require that the family of tests in question be disabl= ed across all platforms.

In the case of KDE Connec= t, as part of it's configure process it runs an external command that r= esults in dbus-daemon being launched. This process persists following the b= uild and would only be cleaned up by our tooling that runs tests. Should th= e 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.= =C2=A0

As this is an issue that has occurred previ= ously, I require that the configure time check which is launching dbus-daem= on 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
--0000000000007f67cf05c4f2f28a--