From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH 2/3] CI: make gitlab-ci build verbose instead of quiet
Date: Sat, 21 Sep 2019 12:36:39 +0200 [thread overview]
Message-ID: <32a6c1e3-5028-df8a-8127-ea1828082c29@siemens.com> (raw)
In-Reply-To: <20190919170403.21809-3-henning.schild@siemens.com>
On 19.09.19 19:04, [ext] Henning Schild wrote:
> From: Henning Schild <henning.schild@siemens.com>
>
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
> ---
> .gitlab-ci.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 1c6fa84..cfd5f91 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -10,4 +10,4 @@ all:
> - export https_proxy=$HTTPS_PROXY
> - export ftp_proxy=$FTP_PROXY
> - export no_proxy=$NO_PROXY
> - - scripts/ci_build.sh -q -f
> + - scripts/ci_build.sh -f
>
Now I remember the reason...
NACK, at least until non-verbose mode is fixed to not interleave the output of
parallel tasks.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-09-21 10:36 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 [this message]
2019-10-15 10:48 ` Baurzhan Ismagulov
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=32a6c1e3-5028-df8a-8127-ea1828082c29@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--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