[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-frameworks-devel
Subject: Re: Notice of withdrawal of CI services: KDevelop and KDE Connect
From: Avamander <avamander () gmail ! com>
Date: 2021-06-16 19:25:30
Message-ID: CAPLrxsHHxgUD+TffLxww=vE97jLG=j56V9HnhEPwWsDBbOA6rQ () mail ! gmail ! com
[Download RAW message or body]
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 =F0=9F=A4=AA
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 <bcooksley@kde.org> 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 prevent=
s
> 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 wi=
ll
> 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 K=
DE
> 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
>
[Attachment #3 (text/html)]
<div dir="ltr">Hi,<br><div><br></div><div>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 <b>FIVE</b> 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 \
🤪<br><br></div><div>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.<br></div><div><br></div><div><br></div><div><br></div><div>Have an extra \
day,</div><div>Avamander</div></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Wed, Jun 16, 2021 at 9:29 PM Ben Cooksley <<a \
href="mailto:bcooksley@kde.org">bcooksley@kde.org</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi all,<div><br></div><div>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:</div><div><br></div><div>- KDevelop</div><div>- KDE \
Connect</div><div><br></div><div>This withdrawal will be applied to all \
platforms.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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. </div><div><br></div><div>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.</div><div><br></div><div>As \
a reminder to all projects, running commands that interact with dbus-daemon or \
kdeinit is not permitted during configure or build \
time.</div><div><br></div><div>Regards,</div><div>Ben Cooksley</div><div>KDE \
Sysadmin</div></div> </blockquote></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic