public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Maiolino <cmaiolino@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfstests should still make xfs as default?
Date: Tue, 9 Apr 2013 11:03:59 -0300	[thread overview]
Message-ID: <20130409140358.GA27522@andromeda.usersys.redhat.com> (raw)
In-Reply-To: <20130408230733.GB17758@dastard>

On Tue, Apr 09, 2013 at 09:07:34AM +1000, Dave Chinner wrote:
> On Wed, Mar 27, 2013 at 05:32:32PM -0300, Carlos Maiolino wrote:
> > Hi, working on xfstests after its new directory structures I noticed we should
> > use now something like:
> > 
> > ./check xfs/<test>
> > 
> > to run some tests, IMHO this is not intuitive and I was working on a patch to
> > make us able to use something just like the old way:
> > 
> > ./check <test>
> 
> What do you do with duplicate test names?
> 
> The main reason that the interface changed was to keep the changes
> to the test harness down to a minimum as it was just moving tests
> around. All that code needs to be revisited to support arbitrary
> test names, so there wasn't much point in doing a massive rework
> only to have to rework it again...
> 
> But the question is: is the old way a sane way to specify tests in
> the brave new world? I'd much prefer that test specification is
> explict, and doesn't implicitly select tests. Indeed, if it
> implicitly selects tests (e.g. when there are duplicates it runs all
> duplicates) then we still need a method for running specific
> tests.....
> 
> Note that what you are seeing is how the $have_test_arg code
> processes the test name. It requires that you tell it the directory
> so it knows where to look for the specific test. You could make it
> look in each test directory like get_group_list()/get_all_tests() do
> so we don't need to specify a directory.
> 
> > But, since xfstests is becoming more generalist than xfs specific, I wonder if
> > we should still keep xfs as default.
> 
> The default is whatever filesystem is on the $TEST_DEV, and I don't
> see that changing. i.e. what we set FSTYP to is the default. Note
> that get_group_list() and get_all_tests() specifically include the
> FSTYP directory,
> 
Hi, this makes sense to me Dave, thanks to the explanation.

We have some documentation which says xfstests will run tests for a xfs
filesystem by default if no other fstype is specified, I'll change this into
documentation then.

Cheers,

-- 
Carlos

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2013-04-09 14:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 20:32 xfstests should still make xfs as default? Carlos Maiolino
2013-04-08 23:07 ` Dave Chinner
2013-04-09 14:03   ` Carlos Maiolino [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=20130409140358.GA27522@andromeda.usersys.redhat.com \
    --to=cmaiolino@redhat.com \
    --cc=david@fromorbit.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