From: Anand Jain <Anand.Jain@oracle.com>
To: Hugo Mills <hugo@carfax.org.uk>,
Chris Mason <chris.mason@oracle.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Arne Jansen <sensille@gmx.net>
Subject: Re: Btrfs progs git repo on kernel.org
Date: Fri, 28 Oct 2011 10:23:19 +0800 [thread overview]
Message-ID: <4EAA1217.50904@oracle.com> (raw)
In-Reply-To: <20111027214811.GL29548@carfax.org.uk>
>>> I've also got the basis of a set of regression tests for -progs,
>>> which I'll send out patches for in the next couple of days. At the
>>> moment, it only tests building and snapshots, but should be relatively
>>> easily extensible to the other bits of ./btrfs (although I'm not sure
>>> how we can easily and repeatably test the recovery tools).
>>
>> Please talk with Anand Jain on the test programs, he has been making
>> scripts for xfs-tests.
>
> Will do, although I think we're aiming at different things. I'm
> very definitely *not* attempting to test the filesystem itself with my
> test harness. I just want to exercise all the bits of the userspace
> tools that I can. (This was primarily triggered by the mess
> surrounding the parsing of "btrfs sub snap" parameters).
Testing the (btrfs) CLI wasn't aimed in the xfs-tests instead the
FS itself.
Appears that btrfs CLI syntax-change is upcoming what we might also
need is a CLI to check the version of both btrfs and btrfs-progs
to ensure tools surrounding them will report -incompatible instead
of syntax error.
thanks. -Anand
next prev parent reply other threads:[~2011-10-28 2:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 15:27 Btrfs progs git repo on kernel.org Chris Mason
2011-10-27 15:58 ` Hugo Mills
2011-10-27 21:32 ` Chris Mason
2011-10-27 21:48 ` Hugo Mills
2011-10-28 2:23 ` Anand Jain [this message]
2011-10-28 16:27 ` Sergei Trofimovich
2011-10-29 5:07 ` Chris Mason
2011-11-15 15:12 ` Phillip Susi
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=4EAA1217.50904@oracle.com \
--to=anand.jain@oracle.com \
--cc=chris.mason@oracle.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=sensille@gmx.net \
/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).