[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:       Ben Cooksley <bcooksley () kde ! org>
Date:       2021-06-17 9:25:15
Message-ID: CA+XidOEJi6NEy8xrBQKE4rkYDNeZynjjiiWDNvFeMSWdwoNcrw () mail ! gmail ! com
[Download RAW message or body]

On Thu, Jun 17, 2021 at 8:44 AM Milian Wolff <mail@milianw.de> wrote:

> 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,
>

Hi Milian,


>
> 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...
>

The issue in question was noted on #kdevelop (prior to the whole Freenode
meltdown) on a few occasions.


>
> 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.
>

I'm afraid I only have records of the hung test processes (and the gdb
processes above them using an entire CPU core indefinitely each).

jenkins    60635   0.0  0.0   12120   2256  0  TXs+ 02:44         0:00.00
/usr/home/jenkins/workspace/KDevelop/kdevelop/kf5-qt5
FreeBSDQt5.15/build/plugins/debuggercommon/tests/debuggees/debuggee_debugeeslow
(debuggee_debugeeslo)
jenkins    74167   0.0  0.0   12120   2260  1  TXs+ 02:55         0:00.00
/usr/home/jenkins/workspace/KDevelop/kdevelop/kf5-qt5
FreeBSDQt5.15/build/plugins/debuggercommon/tests/debuggees/debuggee_debugeeslow
(debuggee_debugeeslo)

Hopefully that is enough to identify the tests that are broken?


>
> Cheers and thanks for letting me know about this problem
>
> --
> Milian Wolff
> mail@milianw.de
> http://milianw.de


Thanks,
Ben

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Thu, Jun 17, 2021 at 8:44 AM Milian Wolff &lt;<a \
href="mailto:mail@milianw.de">mail@milianw.de</a>&gt; wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mittwoch, 16. Juni \
2021 20:28:25 CEST Ben Cooksley wrote:<br> &gt; Hi all,  </blockquote><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> &gt; <br>
&gt; The following is notice that I intend to withdraw CI services from the<br>
&gt; following two KDE projects due to faults in their code or build system<br>
&gt; which are having a significant adverse impact on the CI system and<br>
&gt; negatively impacting on other projects:<br>
&gt; <br>
&gt; - KDevelop<br>
&gt; - KDE Connect<br>
&gt; <br>
&gt; This withdrawal will be applied to all platforms.<br>
&gt; <br>
&gt; In the case of KDevelop, it has a series of unit tests which on FreeBSD<br>
&gt; cause gdb to hang and consume an entire CPU core indefinitely. This slows<br>
&gt; down builds for all other projects using that CI server, and also prevents<br>
&gt; KWin tests from proceeding - completely blocking it&#39;s jobs. This fault \
is<br> &gt; in the debuggee_slow family of tests.<br>
<br>
Hey Ben,<br></blockquote><div><br></div><div>Hi Milian,</div><div>  </div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> <br>
first time I hear of this issue. I simply don&#39;t have the capacity to track <br>
kdevelop CI mails, so if anything really bad happens, I would really <br>
appreciate if anyone who notices that sents a mail to the kdevelop mailing <br>
list so we can act on it. I still use kdevelop daily, but don&#39;t put any other \
<br> work in it currently due to lack of \
time...<br></blockquote><div><br></div><div>The issue in question was noted on \
#kdevelop (prior to the whole Freenode meltdown) on a few occasions.  </div><div>  \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px \
solid rgb(204,204,204);padding-left:1ex"> <br>
That said: can we just disable it on the FreeBSD platform, if that&#39;s the only \
<br> one that exhibits this failure? Alternatively I&#39;m obviously fine with \
skipping <br> that test on that platform, can you give me a link to a failure please \
so I <br> can see which tests exactly are affected? Then I&#39;ll add the QSKIP + \
platform <br> ifdef checks to skip it on \
freebsd.<br></blockquote><div><br></div><div>I&#39;m afraid I only have records of \
the hung test processes (and the gdb processes above them using an entire CPU core \
indefinitely each).</div><div><br></div><div>jenkins      60635    0.0   0.0    12120 \
2256   0   TXs+ 02:44             0:00.00 \
/usr/home/jenkins/workspace/KDevelop/kdevelop/kf5-qt5 \
FreeBSDQt5.15/build/plugins/debuggercommon/tests/debuggees/debuggee_debugeeslow \
(debuggee_debugeeslo)<br>jenkins      74167    0.0   0.0    12120    2260   1   TXs+ \
02:55             0:00.00 /usr/home/jenkins/workspace/KDevelop/kdevelop/kf5-qt5 \
FreeBSDQt5.15/build/plugins/debuggercommon/tests/debuggees/debuggee_debugeeslow \
(debuggee_debugeeslo)<br></div><div><br></div><div>Hopefully that is enough to \
identify the tests that are broken?</div><div>  </div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> <br>
Cheers and thanks for letting me know about this problem<br>
<br>
-- <br>
Milian Wolff<br>
<a href="mailto:mail@milianw.de" target="_blank">mail@milianw.de</a><br>
<a href="http://milianw.de" rel="noreferrer" \
target="_blank">http://milianw.de</a></blockquote><div><br></div><div>Thanks,</div><div>Ben \
</div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic