public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 2/2] scripts: return errors for CI
Date: Fri, 9 Mar 2018 09:30:51 +0100	[thread overview]
Message-ID: <20180309093051.7bb79579@mmd1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <20180309082128.11093-2-henning.schild@siemens.com>

I just saw something similar on the list.

Henning

Am Fri, 9 Mar 2018 09:21:28 +0100
schrieb Henning Schild <henning.schild@siemens.com>:

> I received mail from Jenkins looking like that:
> 
> > Test: FAIL  
> ...
> > Test: FAIL  
> ...
> > POST BUILD TASK : SUCCESS  
> 
> This patch actually collects the number of failing qemus and returns
> it, so the caller can react on it.
> 
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
> ---
>  scripts/vm_smoke_test | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/scripts/vm_smoke_test b/scripts/vm_smoke_test
> index 3bcfd5a..f1bd411 100755
> --- a/scripts/vm_smoke_test
> +++ b/scripts/vm_smoke_test
> @@ -6,6 +6,8 @@
>  CONSOLE_OUTPUT=/tmp/isar_console
>  PID_FILE=/tmp/qemu.pid
>  
> +ret=0
> +
>  check_output() {
>      str=$(tail -1 $CONSOLE_OUTPUT)
>  
> @@ -13,6 +15,7 @@ check_output() {
>          echo "Test: PASSED"
>      else
>          echo "Test: FAIL"
> +	ret=`expr $ret + 1`
>      fi
>  }
>  
> @@ -48,3 +51,5 @@ run_test amd64 stretch
>  # i386 machine
>  run_test i386 jessie
>  run_test i386 stretch
> +
> +exit $ret


  reply	other threads:[~2018-03-09  8:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09  8:21 [PATCH 1/2] meta: image: detect broken symlinks Henning Schild
2018-03-09  8:21 ` [PATCH 2/2] scripts: return errors for CI Henning Schild
2018-03-09  8:30   ` Henning Schild [this message]
2018-03-09  8:30 ` [PATCH 1/2] meta: image: detect broken symlinks Henning Schild

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=20180309093051.7bb79579@mmd1pvb1c.ad001.siemens.net \
    --to=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