From: Josef Bacik <jbacik@fusionio.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: Filipe David Manana <fdmanana@gmail.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: separate out tests into their own directory
Date: Thu, 15 Aug 2013 09:56:21 -0400 [thread overview]
Message-ID: <20130815135621.GF26269@localhost.localdomain> (raw)
In-Reply-To: <20130815133833.GE26269@localhost.localdomain>
On Thu, Aug 15, 2013 at 09:38:33AM -0400, Josef Bacik wrote:
> On Thu, Aug 15, 2013 at 01:23:53AM +0100, Filipe David Manana wrote:
> > On Wed, Aug 14, 2013 at 8:28 PM, Josef Bacik <jbacik@fusionio.com> wrote:
> > > The plan is to have a bunch of unit tests that run when btrfs is loaded when you
> > > build with the appropriate config option. My ultimate goal is to have a test
> > > for every non-static function we have, but at first I'm going to focus on the
> > > things that cause us the most problems. To start out with this just adds a
> > > tests/ directory and moves the existing free space cache tests into that
> > > directory and sets up all of the infrastructure. Thanks,
> > >
> > > Signed-off-by: Josef Bacik <jbacik@fusionio.com>
> >
> > Josef this seems to have broke compilation when sanity checks are not enabled.
> > The following patch fixes it for me at least. Thanks.
> >
>
> Weird that's what I committed but not what I sent to the list, sorry about that.
> Thanks,
>
Oh I see, I didn't actually commit it, oops.
Josef
prev parent reply other threads:[~2013-08-15 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 19:28 [PATCH] Btrfs: separate out tests into their own directory Josef Bacik
2013-08-15 0:23 ` Filipe David Manana
2013-08-15 13:38 ` Josef Bacik
2013-08-15 13:56 ` Josef Bacik [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=20130815135621.GF26269@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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).