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 14:19:41 +0200 [thread overview]
Message-ID: <20191015121941.cnk35jzmef5djctr@yssyq.m.ilbers.de> (raw)
In-Reply-To: <1601e8f5-8219-f7f8-b687-dd21955de6fa@siemens.com>
On Tue, Oct 15, 2019 at 01:31:24PM +0200, Jan Kiszka wrote:
> 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.
The patch is not applied. You raised the question of fixing interleaved output,
and I shared my opinion. I'm aware of [1], but it doesn't show concurrency in
the same way.
> Believe me, I've
> debugged a number of races seen in CI originally just recently.
Could you perhaps share your experience, what was the key to finding them?
> [1]
> https://github.com/ilbers/isar/commit/e5b7d62f91b233f85361d49871cf9a3dad5b2436
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-10-15 12:19 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
2019-10-15 11:31 ` Jan Kiszka
2019-10-15 12:19 ` Baurzhan Ismagulov [this message]
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=20191015121941.cnk35jzmef5djctr@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