From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 2/3] CI: make gitlab-ci build verbose instead of quiet
Date: Tue, 15 Oct 2019 12:48:44 +0200 [thread overview]
Message-ID: <20191015104844.a6eodbfewfq23lqa@yssyq.m.ilbers.de> (raw)
In-Reply-To: <32a6c1e3-5028-df8a-8127-ea1828082c29@siemens.com>
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.
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.
next prev parent reply other threads:[~2019-10-15 10:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 17:04 [PATCH 0/3] various random style fixes Henning Schild
2019-09-19 17:04 ` [PATCH 1/3] ci_build: cosmetic change to increase readability Henning Schild
2019-10-14 14:11 ` Baurzhan Ismagulov
2019-09-19 17:04 ` [PATCH 2/3] CI: make gitlab-ci build verbose instead of quiet Henning Schild
2019-09-21 10:36 ` Jan Kiszka
2019-10-15 10:48 ` Baurzhan Ismagulov [this message]
2019-10-15 11:31 ` Jan Kiszka
2019-10-15 12:19 ` Baurzhan Ismagulov
2019-09-19 17:04 ` [PATCH 3/3] meta: rootfs: align the name of the apt preferences file for isar-apt Henning Schild
2019-10-15 10:41 ` Baurzhan Ismagulov
2019-09-19 17:38 ` [PATCH 0/3] various random style fixes Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191015104844.a6eodbfewfq23lqa@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox