public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: fstests <fstests@vger.kernel.org>,
	"Darrick J . Wong" <darrick.wong@oracle.com>
Subject: Re: [PATCH] fstests: _fail test by default when _scratch_mount fails
Date: Thu, 22 Feb 2018 14:02:12 +0800	[thread overview]
Message-ID: <20180222060212.GU18267@eguan.usersys.redhat.com> (raw)
In-Reply-To: <CAHc6FU46AetuDG42ymogfPwz2j5j60Fw=urxd14wcfyaWb+9fw@mail.gmail.com>

On Wed, Feb 21, 2018 at 11:27:01AM +0100, Andreas Gruenbacher wrote:
> On 18 February 2018 at 13:44, Eryu Guan <eguan@redhat.com> wrote:
> > Previously _scratch_mount didn't check the mount status and most
> > tests continue to run even if the mount failed (unless test checks
> > for the mount status explicitly). This would result in running tests
> > on the underlying filesystem (usually rootfs) and implicit test
> > failures, and such failures can be annoying and are usually hard to
> > debug.
> >
> > Now _fail test by default if _scratch_mount failed and introduce
> > _try_scratch_mount for tests that need to check mount results
> > themselves. Also introduce a new _try_scratch_mount helper that does
> > scratch mount without checking mount status for tests that do the
> > check themselves.
> 
> The message above doesn't look quite right, but the patch looks good.

Ah, I'll fix that up.

> 
> Reviewed-by: Andreas Gruenbacher <agruenba@redhat.com>

Thanks for review!

Eryu

      reply	other threads:[~2018-02-22  6:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-18 12:44 [PATCH] fstests: _fail test by default when _scratch_mount fails Eryu Guan
2018-02-20 17:20 ` Darrick J. Wong
2018-02-21 10:27 ` Andreas Gruenbacher
2018-02-22  6:02   ` Eryu Guan [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=20180222060212.GU18267@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=agruenba@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=fstests@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox