On 9/12/12 6:15 PM, Brad Figg wrote:
> I'm going to be doing some new runs so anything I find will be reported.
Dave Chinner also pointed out that i.e.
seems to redefine, re-group, exclude etc various tests, and is taking
"intelligence" out of the test suite itself.
I'd be wary of that; xfstests is dynamic - things get fixed, tests get added,
groups changed, etc.
If you hard code for example "this test is for xfs" somewhere else, you might
miss updates which add coverage.
Another example :
#'197' : ['xfs'],# This test is only valid on 32 bit machines
but the test handles that gracefully:
if [ "$bitsperlong" -ne 32 ]; then
_notrun "This test is only valid on 32 bit machines"
In general any test should be runnable; it may then issue 'not run' for some
reason or other, but there's no harm in it - not as much harm as skipping
regression tests because some config file got out of date...
#'275' : ['generic'] # ext4 fails
but I just fixed that one up, and it should pass now. Who will update the 3rd
Failing tests absolutely should be run as well. That information is as
valuable as passing tests. The goal is getting a complete picture, not just a
series of "pass" results. :)