qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH 2/2] docker: Enable features explicitly in test-full
Date: Thu, 7 Sep 2017 22:04:20 +0800	[thread overview]
Message-ID: <20170907140420.GE25123@lemon.lan> (raw)
In-Reply-To: <c839e15b-c486-fd7b-f3f6-deb1b7eb85f1@redhat.com>

On Thu, 09/07 08:37, Eric Blake wrote:
> On 09/07/2017 03:11 AM, Fam Zheng wrote:
> > Also avoid "set -e".
> > 
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > ---
> >  tests/docker/test-full | 80 ++++++++++++++++++++++++++++++++++++++++++++++----
> >  1 file changed, 75 insertions(+), 5 deletions(-)
> > 
> > diff --git a/tests/docker/test-full b/tests/docker/test-full
> > index 05f0d491d1..bd095ad91b 100755
> > --- a/tests/docker/test-full
> > +++ b/tests/docker/test-full
> > @@ -1,8 +1,8 @@
> > -#!/bin/bash -e
> > +#!/bin/bash
> 
> When you drop 'set -e'...
> 
> >  #
> > -# Compile all the targets.
> > +# Compile all the targets with as many features enabled as possible
> >  #
> > -# Copyright (c) 2016 Red Hat Inc.
> > +# Copyright 2016, 2017 Red Hat Inc.
> >  #
> >  # Authors:
> >  #  Fam Zheng <famz@redhat.com>
> > @@ -15,5 +15,75 @@
> >  
> >  cd "$BUILD_DIR"
> 
> ...then you should explicitly check for failure after commands where you
> really do not want to continue execution if they failed.  I'd write this:

We can probably tolerate the failure of cd, but it might be better if we are
strict on that. Will update.

Fam

      reply	other threads:[~2017-09-07 14:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07  8:11 [Qemu-devel] [PATCH 0/2] docker: Update ubuntu and test-full for more coverage Fam Zheng
2017-09-07  8:11 ` [Qemu-devel] [PATCH 1/2] docker: Update ubuntu image Fam Zheng
2017-09-07  8:11 ` [Qemu-devel] [PATCH 2/2] docker: Enable features explicitly in test-full Fam Zheng
2017-09-07 13:37   ` Eric Blake
2017-09-07 14:04     ` Fam Zheng [this message]

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=20170907140420.GE25123@lemon.lan \
    --to=famz@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=eblake@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).