From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>,
Maksim Osipov <mosipov@ilbers.de>
Subject: Re: [PATCH] ci: Terminate ci_build.sh on errors
Date: Mon, 17 Dec 2018 15:58:45 +0100 [thread overview]
Message-ID: <ab59b6f7-c982-1c27-32c0-187e569d6b6a@siemens.com> (raw)
In-Reply-To: <8b12bace-ea34-bfaf-b633-a924e30997bf@siemens.com>
On 17.12.18 09:30, [ext] Jan Kiszka wrote:
> Otherwise, we may paper over real problems.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>
> We may have a bug in next (which revealed this bug), currently
> reproducing without local patches.
>
Fortunately, the second issue turned out to be local-only.
Jan
> scripts/ci_build.sh | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
> index 62092ca..f3523e8 100755
> --- a/scripts/ci_build.sh
> +++ b/scripts/ci_build.sh
> @@ -5,6 +5,8 @@
>
> #!/bin/sh
>
> +set -e
> +
> ES_BUG=3
>
> # Export $PATH to use 'parted' tool
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-12-17 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 8:30 Jan Kiszka
2018-12-17 14:58 ` Jan Kiszka [this message]
2018-12-19 11:43 ` Maxim Yu. Osipov
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=ab59b6f7-c982-1c27-32c0-187e569d6b6a@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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