All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org, eguan@redhat.com
Subject: Re: [PATCH] xfs: change return value check to golden image check
Date: Fri, 19 Feb 2016 12:33:16 +1100	[thread overview]
Message-ID: <20160219013316.GW14668@dastard> (raw)
In-Reply-To: <1455208656-16637-1-git-send-email-zlang@redhat.com>

On Fri, Feb 12, 2016 at 12:37:36AM +0800, Zorro Lang wrote:
> xfs/133 and xfs/138 use too much code to do "return value" check,
> it's not necessary. For the code can be more readable and clear,
> I change "return value" check to golden image check.
> 
> Signed-off-by: Zorro Lang <zlang@redhat.com>
> ---
>  tests/xfs/133     | 20 +++++++-------------
>  tests/xfs/133.out |  7 +++++++
>  tests/xfs/138     | 26 ++++++++++++--------------
>  tests/xfs/138.out | 12 ++++++++++++
>  4 files changed, 38 insertions(+), 27 deletions(-)

This cause a xfs/133 failure like this on my systems:

--- tests/xfs/133.out   2016-02-19 10:40:57.043131919 +1100
+++ /home/dave/src/xfstests-dev/results//xfs/xfs/133.out.bad    2016-02-19 12:24:53.173589432 +1100
@@ -4,5 +4,6 @@
 Filesystem Blocks Quota Limit Warn/Time Mounted on
 SCRATCH_DEV 0 102400 204800 00 [--------] SCRATCH_MNT
 === report command output ===
+(null) 0 0 0 00 [--------]
 123456-project 0 102400 204800 00 [--------]
 

Can you see if you can reproduce it?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2016-02-19  1:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 16:37 [PATCH] xfs: change return value check to golden image check Zorro Lang
2016-02-19  1:33 ` Dave Chinner [this message]
2016-02-19 15:06   ` Zirong Lang
2016-02-21  0:18     ` Dave Chinner
2016-02-19 15:35   ` Zirong Lang
2016-02-19 15:43     ` Zirong Lang
2016-02-19 15:58     ` Eric Sandeen
2016-02-19 16:35       ` Eric Sandeen
2016-02-19 16:52         ` Zirong Lang
2016-02-19 17:07           ` Zirong Lang
2016-02-19 17:16             ` Eric Sandeen

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=20160219013316.GW14668@dastard \
    --to=david@fromorbit.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=zlang@redhat.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 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.