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

List:       kde-core-devel
Subject:    Re: CI log verbosity
From:       Ingo =?ISO-8859-1?Q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2023-11-03 13:47:45
Message-ID: 5727980.DvuYhMxLoT () daneel
[Download RAW message or body]


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

> 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

["signature.asc" (application/pgp-signature)]

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