From: Eryu Guan <eguan@redhat.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] xfs: Make 'man' hard requirement for xfs/293
Date: Tue, 23 May 2017 22:01:56 +0800 [thread overview]
Message-ID: <20170523140156.GD7250@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1495539943-9670-1-git-send-email-nborisov@suse.com>
On Tue, May 23, 2017 at 02:45:43PM +0300, Nikolay Borisov wrote:
> If xfs/293 is run on a system which doesn't have 'man' installed
> it will hang the due to $CAT waiting for input indefinitely
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Yeah, we need to make sure 'man' is available.
>
> ---
> tests/xfs/293 | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tests/xfs/293 b/tests/xfs/293
> index df44e98e..9556b4bb 100755
> --- a/tests/xfs/293
> +++ b/tests/xfs/293
> @@ -40,6 +40,8 @@ _cleanup()
> . ./common/rc
> . ./common/filter
>
> +_require_command man man
> +
Can you please add an entry in common/config for $MAN_PROG and do the
check in xfs/293 *after* _supported_os call, and call $MAN_PROG instead
of bare 'man'?
Thanks,
Eryu
> # real QA test starts here
>
> # Modify as appropriate.
> --
> 2.12.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-23 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 11:45 [PATCH] xfs: Make 'man' hard requirement for xfs/293 Nikolay Borisov
2017-05-23 14:01 ` Eryu Guan [this message]
2017-05-23 14:16 ` [PATCH v2] " Nikolay Borisov
2017-05-23 14:32 ` 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=20170523140156.GD7250@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=nborisov@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox