From: Christoph Hellwig <hch@infradead.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Steve Long <slong@rathaus.eclipse.co.uk>, linux-btrfs@vger.kernel.org
Subject: Re: Testsuite (was: Re: Hi!)
Date: Mon, 25 Aug 2008 13:15:14 -0400 [thread overview]
Message-ID: <20080825171514.GA15530@infradead.org> (raw)
In-Reply-To: <1219667498.28188.4.camel@think.oraclecorp.com>
On Mon, Aug 25, 2008 at 08:31:38AM -0400, Chris Mason wrote:
> On Mon, 2008-08-25 at 10:06 +0100, Steve Long wrote:
> > > Testing, discussing and reporting bugs are a great first step.
> > >
> > Just wondering whether btrfs has, or might want, something like this:
> > http://blogs.sun.com/bill/entry/zfs_and_the_all_singing
> >
> > I don't have anything like it from btrfs-progs, apart from btrfs-debug-tree.
> > I'm sure you're doing tests internally and users are testing stuff too;
> > formalising it a bit and collaborating on that element might be useful?
> >
> > (Apologies if I'm missing something obvious.)
>
> We don't have an official test suite yet, but a few people are working
> on various parts of it. It is definitely an area where collaboration is
> useful and needed.
And I'd like to again say that if you want to start on a testsuite it
might be a good idea to extend the xfs testsuite. It already deals with
udf and partially nfs and having one testsuite to run on multiple
filesystems is always a good idea. It already supports testcases
specific to a certain filesystem or OS.
prev parent reply other threads:[~2008-08-25 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 8:43 Hi! Eric Anopolsky
2008-08-20 18:25 ` Hi! Chris Mason
2008-08-21 10:47 ` Hi! Miguel Sousa Filipe
2008-08-24 7:02 ` Hi! Steve Long
2008-08-25 21:56 ` Hi! Miguel Sousa Filipe
2008-09-04 19:07 ` Testsuite Steve Long
2008-08-25 9:06 ` Testsuite (was: Re: Hi!) Steve Long
2008-08-25 12:31 ` Chris Mason
2008-08-25 17:15 ` Christoph Hellwig [this message]
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=20080825171514.GA15530@infradead.org \
--to=hch@infradead.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=slong@rathaus.eclipse.co.uk \
/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