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

List:       kde-core-devel
Subject:    Re: CI log verbosity
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2023-11-04 9:09:02
Message-ID: CA+XidOFhbfgY38vOsRiZ0=T0D7xVjOuiaKNN-9s-sGo73_KpEA () mail ! gmail ! com
[Download RAW message or body]

On Sat, Nov 4, 2023 at 2:48 AM Ingo Klöcker <kloecker@kde.org> wrote:

> On Freitag, 3. November 2023 13:01:26 CET Harald Sitter wrote:
> > What are your thoughts on having the CI be less verbose by default and
> > instead have an env var or some other toggle to switch into verbose
> > mode?
>
> +1
>
> Ideally, the verbose logs would be written to an artifact. Otherwise, it
> will
> be painful to debug intermittent problems. I think the Craft jobs now do
> this
> (also in response to insanely verbose output of some builds which made it
> impossible to see the actual error).
>

Unfortunately the test log output is all governed by CMake/CTest so there
isn't too much we can do ourselves - not without doing quite a bit of work
to read XML files produced by CTest anyway.


>
> > Specifically I'm talking about the qtlogging rules that are currently
> > enabling everything and the kitchen sink. To my mind we should just
> > use the default rules by default.
> > I find that 99% of the time the output is entirely useless in finding
> > what is wrong, if anything it gets in the way because I first have to
> > find where the test failure is and then instead of reading walls of qt
> > plugin info I will just proceed to reproduce the problem locally
> > anyway.
>
> Full ACK. I'm almost always only interested in finding the error which
> caused
> the CI job to fail and sometimes in seeing compiler warnings.
>
> Regards,
> Ingo
>

Cheers,
Ben

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Sat, Nov 4, 2023 at 2:48 AM Ingo Klöcker &lt;<a \
href="mailto:kloecker@kde.org">kloecker@kde.org</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 Freitag, 3. \
November 2023 13:01:26 CET Harald Sitter wrote:<br> &gt; What are your thoughts on \
having the CI be less verbose by default and<br> &gt; instead have an env var or some \
other toggle to switch into verbose<br> &gt; mode?<br>
<br>
+1<br>
<br>
Ideally, the verbose logs would be written to an artifact. Otherwise, it will <br>
be painful to debug intermittent problems. I think the Craft jobs now do this <br>
(also in response to insanely verbose output of some builds which made it <br>
impossible to see the actual \
error).<br></blockquote><div><br></div><div>Unfortunately the test log output is all \
governed by CMake/CTest so there isn&#39;t too much we can do ourselves - not without \
doing quite a bit of work to read XML files produced by CTest anyway.</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>
&gt; Specifically I&#39;m talking about the qtlogging rules that are currently<br>
&gt; enabling everything and the kitchen sink. To my mind we should just<br>
&gt; use the default rules by default.<br>
&gt; I find that 99% of the time the output is entirely useless in finding<br>
&gt; what is wrong, if anything it gets in the way because I first have to<br>
&gt; find where the test failure is and then instead of reading walls of qt<br>
&gt; plugin info I will just proceed to reproduce the problem locally<br>
&gt; anyway.<br>
<br>
Full ACK. I&#39;m almost always only interested in finding the error which caused \
<br> the CI job to fail and sometimes in seeing compiler warnings.<br>
<br>
Regards,<br>
Ingo<br></blockquote><div><br></div><div>Cheers,</div><div>Ben  </div></div></div>



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