From: Dave Chinner <david@fromorbit.com>
To: Zach Brown <zab@zabbo.net>
Cc: Theodore Ts'o <tytso@mit.edu>, Rich Johnston <rjohnston@sgi.com>,
xfs-oss <xfs@oss.sgi.com>,
linux-ext4@vger.kernel.org,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Announce re-factor all current xfstests patches request
Date: Thu, 28 Mar 2013 11:34:35 +1100 [thread overview]
Message-ID: <20130328003435.GW6369@dastard> (raw)
In-Reply-To: <20130327204217.GC16651@lenny.home.zabbo.net>
On Wed, Mar 27, 2013 at 01:42:17PM -0700, Zach Brown wrote:
> On Wed, Mar 27, 2013 at 03:05:12PM -0400, Theodore Ts'o wrote:
> > What do you think about renaming the existing tests from NNN to
> > NNN-descriptive-name? That way it will be easier for people who are
> > trying to track regressions, since they can easily map from the new
> > more descriptive name to the old test number for comparison purposes
> > (i.e., to see whether a failure is a regression or not, etc.)
>
> It does seem like a good idea to help people map from descriptive names
> to their previous numeric file names.
>
> But do we want to bake it in to the file names forevermore? Would it be
> good enough to start the old tests with something like
>
> _was_test_nr 45
$ cd tests/generic
$ ../../lsqa.pl -b 001
Random file copier to produce chains of identical files so the head
and the tail can be diff'd at the end of each iteration.
Exercises creat, write and unlink for a variety of directory sizes,
and
checks for data corruption.
run [config]
config has one line per file with filename and byte size, else use
the default one below.
$ ../../lsqa.pl -b 005
Test symlinks & ELOOP
$
Do we even really need to change them? Fix the lsqa.pl script be
able to take a directory argument, and just use the script to get
the description....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2013-03-28 0:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 13:23 Announce re-factor all current xfstests patches request Rich Johnston
2013-03-27 13:46 ` Theodore Ts'o
2013-03-27 16:42 ` Rich Johnston
2013-03-27 19:05 ` Theodore Ts'o
2013-03-27 20:42 ` Zach Brown
2013-03-27 20:52 ` Ben Myers
2013-03-28 0:34 ` Dave Chinner [this message]
2013-03-27 21:02 ` Dave Chinner
2013-03-27 20:54 ` Dave Chinner
2013-03-27 21:48 ` Theodore Ts'o
2013-03-28 0:35 ` Dave Chinner
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=20130328003435.GW6369@dastard \
--to=david@fromorbit.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=rjohnston@sgi.com \
--cc=tytso@mit.edu \
--cc=xfs@oss.sgi.com \
--cc=zab@zabbo.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).