linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Nick Krause <xerofoify@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Work on ext4
Date: Fri, 25 Jul 2014 11:41:42 -0400	[thread overview]
Message-ID: <20140725154142.GU1865@thunk.org> (raw)
In-Reply-To: <CAPDOMVgmkoXQxGODzVaYWYykPWVmpG=jyKNbGv5=3BZ=XQnGrg@mail.gmail.com>

On Fri, Jul 25, 2014 at 11:22:02AM -0400, Nick Krause wrote:
> I was being sloppy. I screwed up if you want my help still, please
> let me known.

Well, tell you what.  Why don't you start by downloading the following
git repository:

git://git.kernel.org/pub/scm/fs/ext2/xfstests-bld.git

And then start by trying to use kvm-xfstests.  There are some tests
which are known failures; some are false positives, some are just bugs
that we haven't gotten around to fixing.  (This is especially true for
bigalloc, which has a number of failures that still need to be tracked
down.)

The main rule that we follow is that we don't want to see any
regressions.  So extending kvm-xfstests by writing a script which
analyzes the output of the get-results scripts so that regressions can
be automatically flagged would be a good and useful thing to add.

Another thing that would be useful is a script which automates using
kvm-xfstests to drive "git bisect".  Typically what happens after we
discover a regression is to try to check and see of the failure is
easily replicable using a single xfstests, and then to start bisecting
from the baseline run where the test was successful, to try to find
the guilty bisect.  Automating this would be very useful.

This will hopefully get you started on the testing side of things,
which is also a good way to start learning about how ext4 works.

Cheers,

						- Ted

  reply	other threads:[~2014-07-25 15:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25  2:29 Work on ext4 Nick Krause
2014-07-25 14:59 ` Theodore Ts'o
2014-07-25 15:22   ` Nick Krause
2014-07-25 15:41     ` Theodore Ts'o [this message]
2014-07-25 16:07       ` Eric Sandeen
2014-07-28  4:01         ` Nick Krause
2014-07-28 12:45           ` Theodore Ts'o
2014-07-28 15:17             ` Nick Krause
2014-07-25 15:24 ` Wang Shilong
2014-07-25 15:59   ` Nick Krause
2014-07-25 16:06     ` Nick Krause

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=20140725154142.GU1865@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=xerofoify@gmail.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;
as well as URLs for NNTP newsgroup(s).