From: Eryu Guan <guaneryu@gmail.com>
To: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] generic/469: Skip the test if fallocate keep_size is not supported
Date: Fri, 18 Oct 2019 16:39:55 +0800 [thread overview]
Message-ID: <20191018083951.GJ2622@desktop> (raw)
In-Reply-To: <20191016105347.16650-1-misono.tomohiro@jp.fujitsu.com>
On Wed, Oct 16, 2019 at 07:53:47PM +0900, Misono Tomohiro wrote:
> This test requires fallocate keep_size. So, skip the test if
> a target FS does not support the function to avoid false negative.
>
> Signed-off-by: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>
Would you please paste the false failure you've seen? I can't recall I
hit such failures, and I think fsx would just disable unsupported
operations and don't cause failure, it just prints a message to stderr,
and we already redirect stderr to $seqres.full in run_fsx in 469.
Thanks,
Eryu
> ---
> tests/generic/469 | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/generic/469 b/tests/generic/469
> index 47fdf0cf..0c6f8ae5 100755
> --- a/tests/generic/469
> +++ b/tests/generic/469
> @@ -40,6 +40,7 @@ rm -f $seqres.full
> _supported_fs generic
> _supported_os Linux
> _require_test
> +_require_xfs_io_command "falloc" "-k"
>
> run_fsx()
> {
> --
> 2.21.0
>
next prev parent reply other threads:[~2019-10-18 8:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 10:53 [PATCH] generic/469: Skip the test if fallocate keep_size is not supported Misono Tomohiro
2019-10-17 2:42 ` Yang Xu
2019-10-17 2:52 ` misono.tomohiro
2019-10-17 3:55 ` Yang Xu
2019-10-17 7:08 ` misono.tomohiro
2019-10-18 8:39 ` Eryu Guan [this message]
2019-10-18 9:02 ` misono.tomohiro
2019-10-18 10:24 ` Eryu Guan
2019-10-18 10:52 ` misono.tomohiro
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=20191018083951.GJ2622@desktop \
--to=guaneryu@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=misono.tomohiro@jp.fujitsu.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.