Re: [PATCH 2/3] CI: make gitlab-ci build verbose instead of quiet

[Jan Kiszka <jan.kiszka@siemens.com>]

On 15.10.19 12:48, Baurzhan Ismagulov wrote:
> On Sat, Sep 21, 2019 at 12:36:39PM +0200, Jan Kiszka wrote:
>>> -    - scripts/ci_build.sh -q -f
>>> +    - scripts/ci_build.sh -f
> ...
>> NACK, at least until non-verbose mode is fixed to not interleave the output
>> of parallel tasks.
> 
> I've enabled that on ci.isar-build.org, since it's the only way to see the
> concurrency. This may help debugging sporadic races. I agree that the output is
> very hard to read.

Sigh... If you really think you can read anything out of the resulting
logs in practice (I seriously doubt this), please confine this to your
private Jenkins runs. For gitlab-ci, we neither need this - because of
[1] - nor is it desired as I explained clearly. Believe me, I've
debugged a number of races seen in CI originally just recently.

Thanks,
Jan

> 
> IIRC, I had a discussion with DEBOS (?) people regarding the logs, but we
> didn't go into depth. One approach could be to always log everything (even
> messages that don't go to the console), e.g. into a database (with timestamps,
> task name and number, etc.), and have a tool to display and filter the output.
> 
> With kind regards,
> Baurzhan.
> 

[1]
https://github.com/ilbers/isar/commit/e5b7d62f91b233f85361d49871cf9a3dad5b2436

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux