From: Eric Sandeen <sandeen@redhat.com>
To: dsterba@suse.cz
Cc: Kiran Patil <kirantpatil@gmail.com>,
linux-btrfs@vger.kernel.org, bo.li.liu@oracle.com
Subject: Re: Open for contribution towards xfstests for btrfs
Date: Mon, 07 Jan 2013 12:03:12 -0600 [thread overview]
Message-ID: <50EB0DE0.9040500@redhat.com> (raw)
In-Reply-To: <20130107153132.GH20089@twin.jikos.cz>
On 1/7/13 9:31 AM, David Sterba wrote:
> On Mon, Jan 07, 2013 at 03:48:43PM +0530, Kiran Patil wrote:
>> We have a team of 5 students who would like to contribute to btrfs
>> filesystem testing using xfstests.
>
> By any chance, are these the same people behind
> http://sourceforge.net/projects/btrfstest/ ?
If so, you might want to consider that
http://www.tuxera.com/community/posix-test-suite/
probably already covers some of the tests that "btrfstest" is
(re)writing. i.e.:
+/* Creating Link on non-existing prefix path should return ENOTDIR
and
+/* Creating link on ENAMETOOLONG if either file name exceeds maximum characters
are almost certainly covered in the above posix test suite.
FWIW, that testsuite has a few failures on btrfs (not all unique to btrfs, IIRC):
Test Summary Report
-------------------
/root/pjd-fstest/pjd-fstest-20090130-RC/tests/chown/00.t (Wstat: 0 Tests: 171 Failed: 6)
Failed tests: 84, 88, 141, 145, 149, 153
/root/pjd-fstest/pjd-fstest-20090130-RC/tests/truncate/00.t (Wstat: 0 Tests: 21 Failed: 1)
Failed test: 15
/root/pjd-fstest/pjd-fstest-20090130-RC/tests/xacl/00.t (Wstat: 0 Tests: 45 Failed: 1)
Failed test: 45
-Eric
next prev parent reply other threads:[~2013-01-07 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANT588vv8xYNWGBSZUDu0vui2ZH4QqL7tvQX8zOGof7nucC6_Q@mail.gmail.com>
2013-01-07 10:18 ` Open for contribution towards xfstests for btrfs Kiran Patil
2013-01-07 13:01 ` Liu Bo
2013-01-07 14:36 ` Arne Jansen
2013-01-07 15:31 ` David Sterba
2013-01-07 18:03 ` Eric Sandeen [this message]
2013-01-08 2:03 ` Kiran Patil
2013-01-07 15:58 ` Eric Sandeen
2013-01-07 17:01 ` Kiran Patil
2013-01-07 17:09 ` Kiran Patil
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=50EB0DE0.9040500@redhat.com \
--to=sandeen@redhat.com \
--cc=bo.li.liu@oracle.com \
--cc=dsterba@suse.cz \
--cc=kirantpatil@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.