xfstests: kludge patch for per-dir test number sorting by ./check

[Michael L. Semon]

On 04/22/2013 02:25 PM, Rich Johnston wrote:
> 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

It's a good change request, but on further testing, it seems like my 
kludge patch breaks basic sorting, i.e. `./check generic/003 generic/001 
generic/002` will run the tests in exactly that order.  That's not 
necessarily bad--principle of least surprise--but it means that to get 
the old xfstests sorting behavior, it would have to be sorted using 
another method.

Thanks for considering the need for more control over the order in which 
groups are run.  It's most certainly appreciated.

Thinking out loud:  Is there a disadvantage to setting $SRC_DIR to "." 
instead of "tests"?  It looks like a nice way to get `./check 
tests/generic/001` to run tests/generic/001 instead of issuing "unknown 
test, ignored", but I've tested it only for generic/001 here at work.

Michael

>> 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