[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:07:46
Message-ID: CA+XidOGBzJg9SYn+a5KdcTkQPodRuQBuUrokhQomDi0mS9FjiA () mail ! gmail ! com
[Download RAW message or body]

On Sat, Nov 4, 2023 at 1:01 AM Harald Sitter <sitter@kde.org> 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?
>
> 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.
>

The current approach to enabling all of the debugging information was
adopted a few years back when dfaure was trying to debug some tests.
We were back on Jenkins then though, which made it quite difficult to set
things yourself, unlike what you can do now with Gitlab CI and a work
branch.

Behaviour is changed from
https://invent.kde.org/sysadmin/ci-utilities/-/commit/67e9aaac0f540005834bd61c60abf01eed01cb12

If anyone would like to propose a set of more narrow, sane logging rules
then please send an MR (would suggest that it is wrapped behind a check for
whether the logging rules variable is set already though)

Cheers,
Ben


>
> Thoughts?
>
> HS
>

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Sat, Nov 4, 2023 at 1:01 AM Harald Sitter &lt;<a \
href="mailto:sitter@kde.org">sitter@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">What are your thoughts \
on having the CI be less verbose by default and<br> instead have an env var or some \
other toggle to switch into verbose<br> mode?<br>
<br>
Specifically I&#39;m talking about the qtlogging rules that are currently<br>
enabling everything and the kitchen sink. To my mind we should just<br>
use the default rules by default.<br>
I find that 99% of the time the output is entirely useless in finding<br>
what is wrong, if anything it gets in the way because I first have to<br>
find where the test failure is and then instead of reading walls of qt<br>
plugin info I will just proceed to reproduce the problem locally<br>
anyway.<br></blockquote><div><br></div><div>The current approach to enabling all of \
the debugging information was adopted a few years back when dfaure was trying to \
debug some tests.</div><div>We were back on Jenkins then though, which made it quite \
difficult to set things yourself, unlike what you can do now with Gitlab CI and a \
work branch.</div><div><br></div><div>Behaviour is changed from  <a \
href="https://invent.kde.org/sysadmin/ci-utilities/-/commit/67e9aaac0f540005834bd61c60 \
abf01eed01cb12">https://invent.kde.org/sysadmin/ci-utilities/-/commit/67e9aaac0f540005834bd61c60abf01eed01cb12</a></div><div><br></div><div>If \
anyone would like to propose a set of more narrow, sane logging rules then please \
send an MR (would suggest that it is wrapped behind a check for whether the logging \
rules variable is set already though)</div><div><br></div><div>Cheers,</div><div>Ben  \
</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>
Thoughts?<br>
<br>
HS<br>
</blockquote></div></div>



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