From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org, Andreas Gruenbacher <agruenba@redhat.com>
Subject: Re: [PATCH] fstests: _fail test by default when _scratch_mount fails
Date: Tue, 20 Feb 2018 09:20:21 -0800 [thread overview]
Message-ID: <20180220172021.GB14582@magnolia> (raw)
In-Reply-To: <20180218124457.28597-1-eguan@redhat.com>
On Sun, Feb 18, 2018 at 08:44:57PM +0800, Eryu Guan 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.
>
> Suggested-by: Andreas Gruenbacher <agruenba@redhat.com>
> Signed-off-by: Eryu Guan <eguan@redhat.com>
The common/generic/shared/xfs parts look ok,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
(The ext4/btrfs parts seemed ok at a quick glance, but I'm not as
familiar with them.)
--D
next prev parent reply other threads:[~2018-02-20 17:20 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 [this message]
2018-02-21 10:27 ` Andreas Gruenbacher
2018-02-22 6:02 ` Eryu Guan
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=20180220172021.GB14582@magnolia \
--to=darrick.wong@oracle.com \
--cc=agruenba@redhat.com \
--cc=eguan@redhat.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