From: Rich Johnston <rjohnston@sgi.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/3] xfstests patches
Date: Thu, 14 Mar 2013 12:16:12 -0500 [thread overview]
Message-ID: <514205DC.9040902@sgi.com> (raw)
In-Reply-To: <1363186623-1378-1-git-send-email-sandeen@redhat.com>
On 03/13/2013 09:57 AM, Eric Sandeen wrote:
> 2 pretty simple ones, and a new btrfs test
>
> [PATCH 1/3] xfstests: add 274 to the prealloc group
> [PATCH 2/3] xfstests: keep newlines out of SCRATCH_DEV_POOL
> [PATCH 3/3] xfstests: btrfs tests for basic informational commands
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
This series has been committed.
Thanks
--Rich
commit 2730c49a3e80426167e6f9984b070883dc51d4b6
Author: Eric Sandeen <sandeen@sandeen.net>
Date: Wed Mar 13 19:01:58 2013 +0000
xfstests: btrfs tests for basic informational commands
Run basic btrfs information commands in various ways, performing
sanity tests of: filesystem show, label, sync, and device stats
(sync is included just because it's simple). These are mostly
just smoke tests, although for example show by label & UUID
should verify that the correct fs was shown.
This also adds quite a few new filters to accommodate the output
of the new commands.
Cc: linux-btrfs@vger.kernel.org
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Reviewed-by: Stefan Behrens <sbehrens@giantdisaster.de>
Signed-off-by: <rjohnston@sgi.com>
commit d6e352916fbe835432bac2aa835bac440fe44287
Author: Eric Sandeen <sandeen@redhat.com>
Date: Wed Mar 13 14:57:02 2013 +0000
xfstests: keep newlines out of SCRATCH_DEV_POOL
SCRATCH_DEV_POOL processing actually takes the first
device out for SCRATCH_DEV and leaves the rest in
SCRATCH_DEV_POOL.
I'm not totally sold on that behavior, but for now,
at least don't populate SCRATCH_DEV_POOL with newlines.
Cc: linux-btrfs@vger.kernel.org
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Reviewed-by: <rjohnston@sgi.com>
Signed-off-by: <rjohnston@sgi.com>
commit e279134e14800f1d7b34093a93e304b5bed7ec4d
Author: Eric Sandeen <sandeen@redhat.com>
Date: Wed Mar 13 14:57:01 2013 +0000
xfstests: add 274 to the prealloc group
test 274 does preallocation tests but is not in the prealloc group.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-14 17:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 14:57 [PATCH 0/3] xfstests patches Eric Sandeen
2013-03-13 14:57 ` [PATCH 1/3] xfstests: add 274 to the prealloc group Eric Sandeen
2013-03-13 17:36 ` Rich Johnston
2013-03-13 14:57 ` [PATCH 2/3] xfstests: keep newlines out of SCRATCH_DEV_POOL Eric Sandeen
2013-03-13 17:43 ` Rich Johnston
2013-03-13 17:45 ` Eric Sandeen
2013-03-13 14:57 ` [PATCH 3/3] xfstests: btrfs tests for basic informational commands Eric Sandeen
2013-03-13 15:32 ` Stefan Behrens
2013-03-13 16:17 ` Eric Sandeen
2013-03-13 17:47 ` Rich Johnston
2013-03-13 16:38 ` [PATCH 3/3 V2] " Eric Sandeen
2013-03-13 18:53 ` [PATCH 3/3 V3] " Eric Sandeen
2013-03-13 19:00 ` Stefan Behrens
2013-03-13 19:01 ` [PATCH 3/3 V4] " Eric Sandeen
2013-03-14 13:01 ` Rich Johnston
2013-03-14 13:35 ` Stefan Behrens
2013-03-15 10:16 ` Dave Chinner
2013-03-15 13:46 ` Eric Sandeen
2013-03-15 14:23 ` Rich Johnston
2013-03-15 14:36 ` Eric Sandeen
2013-03-18 13:30 ` Rich Johnston
2013-03-19 14:15 ` Rich Johnston
2013-03-14 17:16 ` Rich Johnston [this message]
2013-03-15 5:43 ` [PATCH 0/3] xfstests patches Dave Chinner
2013-03-15 13:38 ` Rich Johnston
-- strict thread matches above, loose matches on Subject: below --
2011-10-13 0:56 [PATCH 1/3] 263: Functional test case for the btrfs snapshot Dave Chinner
2011-10-18 6:28 ` [PATCH 0/3] xfstests patches Anand Jain
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=514205DC.9040902@sgi.com \
--to=rjohnston@sgi.com \
--cc=sandeen@redhat.com \
--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