From: Rich Johnston <rjohnston@sgi.com>
To: "Michael L. Semon" <mlsemon35@gmail.com>
Cc: xfstests <xfs@oss.sgi.com>
Subject: Re: xfstests: kludge patch for per-dir test number sorting by ./check
Date: Mon, 22 Apr 2013 13:25:29 -0500 [thread overview]
Message-ID: <51758099.9030302@sgi.com> (raw)
In-Reply-To: <516B740A.1050607@gmail.com>
On 04/14/2013 10:29 PM, Michael L. Semon wrote:
> On 04/14/2013 07:26 PM, Dave Chinner wrote:
>> On Sat, Apr 13, 2013 at 04:50:06PM -0400, Michael L. Semon wrote:
>>> I'm trying to get the new xfstests to run the XFS tests first, then
>>
>> The question is why do you want to do this? Is there any specific
>> reason for running the tests in that order?
>>
>> FWIW, if all you want to do is run the xfs tests, run:
>>
>> $ sudo ./check xfs[0-9][0-9][0-9]
>>
>> Cheers,
>>
>> Dave.
>>
>
> Personal preference. I'd like to run both series of tests, sometimes
> attended, sometimes unattended. It's fine if a generic/ test crashes
> the PC while running unattended, but I'd much rather the xfs/ tests have
> first crack at that.
>
> My version of the syntax was `./check xfs/[0-9][0-9][0-9]`, but that
> becomes rough when skipping tests. I'll still try your version, but
I think this is a reasonable change request and I can see how this would
be very rough if you wanted to skip tests. Anyone have a reason why not
to do this?
Regards,
--Rich
> irrationality and frustration have driven me to simply adding a "mls"
> group to all of the tests/<fsgroup>/group files, then hoping that a
> `./check -g mls` would run everything in the correct order. That led to
> trying to figure out why the generic/ tests were running first, and so
> on and so forth...
>
> Thanks!
>
> Michael
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-04-22 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 20:50 xfstests: kludge patch for per-dir test number sorting by ./check Michael L. Semon
2013-04-14 23:26 ` Dave Chinner
2013-04-15 3:29 ` Michael L. Semon
2013-04-22 18:25 ` Rich Johnston [this message]
2013-04-23 14:08 ` Michael L. Semon
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=51758099.9030302@sgi.com \
--to=rjohnston@sgi.com \
--cc=mlsemon35@gmail.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