From: Dave Chinner <david@fromorbit.com>
To: Filipe David Borba Manana <fdmanana@gmail.com>
Cc: xfs@oss.sgi.com, jbacik@fb.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] xfstests: btrfs, add test for btrfs properties
Date: Wed, 16 Apr 2014 10:29:25 +1000 [thread overview]
Message-ID: <20140416002925.GW15995@dastard> (raw)
In-Reply-To: <1397591424-25439-1-git-send-email-fdmanana@gmail.com>
On Tue, Apr 15, 2014 at 08:50:24PM +0100, Filipe David Borba Manana wrote:
> This test case verifies the btrfs properties feature, a new feature
> introduced in the linux kernel version 3.14.
>
> Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com>
...
> ---
> common/rc | 9 +++
> tests/btrfs/048 | 220 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> tests/btrfs/048.out | 78 +++++++++++++++++++
> tests/btrfs/group | 1 +
> 4 files changed, 308 insertions(+)
> create mode 100755 tests/btrfs/048
> create mode 100644 tests/btrfs/048.out
>
> diff --git a/common/rc b/common/rc
> index acf419b..d4ba74f 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -2262,6 +2262,15 @@ _run_btrfs_util_prog()
> run_check $BTRFS_UTIL_PROG $*
> }
>
> +_require_btrfs_properties()
> +{
> + $BTRFS_UTIL_PROG | grep 'btrfs property ' > /dev/null 2>&1
> + if [ $? -ne 0 ]
> + then
> + _notrun "Missing btrfs-progs with properties support, skipped this test"
> + fi
if [ ... ]; then
....
> +seq=`basename $0`
> +seqres=$RESULT_DIR/$seq
> +echo "QA output created by $seq"
> +
> +here="`pwd`"
> +tmp=/tmp/$$
> +
> +status=1 # failure is the default!
> +trap "_cleanup; exit \$status" 0 1 2 3 15
> +
> +send_files_dir=$TEST_DIR/btrfs-test-$seq
You should define this after including the common/* files.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-04-16 0:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 19:50 [PATCH] xfstests: btrfs, add test for btrfs properties Filipe David Borba Manana
2014-04-16 0:29 ` Dave Chinner [this message]
2014-04-16 15:04 ` [PATCH v2] " Filipe David Borba Manana
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=20140416002925.GW15995@dastard \
--to=david@fromorbit.com \
--cc=fdmanana@gmail.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).