All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Gilles Espinasse <g.esp@free.fr>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 1/3] Align FAILED to test name to be parsable
Date: Mon, 22 Oct 2012 09:08:55 +1100	[thread overview]
Message-ID: <20121022090855.1bb52c91@notabene.brown> (raw)
In-Reply-To: <1350749002-5445-1-git-send-email-g.esp@free.fr>

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

On Sat, 20 Oct 2012 18:03:22 +0200 Gilles Espinasse <g.esp@free.fr> wrote:

> Signed-off-by: Gilles Espinasse <g.esp@free.fr>
> 
> So 'grep FAILED log' is now meaningfull.
> Let both stdout and sderr be displayed after a failed test
> ---
>  test |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/test b/test
> index 9340afe..2bb482c 100755
> --- a/test
> +++ b/test
> @@ -222,12 +222,13 @@ do_test() {
>      # source script in a subshell, so it has access to our
>      # namespace, but cannot change it.
>      echo -ne "$_script... "
> -    if ( set -ex ; . $_script )  2> $targetdir/log
> +    if ( set -ex ; . $_script ) &> $targetdir/log
>      then
>        echo "succeeded"
>        _fail=0
>      else
> -      echo "FAILED - see $targetdir/log for details"
> +      echo "FAILED"
> +      cat $targetdir/log
>        _fail=1
>      fi
>      if [ "$savelogs" == "1" ]; then

Hi,
 the patch makes some sense, but it doesn't seem to match the description,
 though maybe I'm just being dense.

 How does the patch "Align FAILED to test name" ?

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-10-21 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20 16:03 [PATCH 1/3] Align FAILED to test name to be parsable Gilles Espinasse
2012-10-21 22:08 ` NeilBrown [this message]
2012-10-22  8:31   ` g.esp
2012-10-22 22:23     ` NeilBrown
2012-10-23  8:31       ` g.esp
2012-11-12  5:48         ` NeilBrown

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=20121022090855.1bb52c91@notabene.brown \
    --to=neilb@suse.de \
    --cc=g.esp@free.fr \
    --cc=linux-raid@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.