On Wed, Oct 22, 2008 at 08:55:13PM +0000, Adam Litke wrote:
> The libhugetlbfs test suite has various tests for which a failure (under
> certain circumstances) is expected and not indicative of an error. It would
> be desirable to specially annotate these cases to eliminate the need for the
> tester to know which failures are known and which could be bugs.
>
> This patch creates some test harness infrastructure that can be used to
> achieve this goal. How does it work? If a test case needs expected failure
> validation, a shell script (named <testcase>.sh) is placed in the tests/
> directory. The test invocation in run_tests.sh is changed to execute the
> shell script instead of the c program directly. The shell script must
> perform any required discovery, execute the real test case, and interpret the
> result.
>
> Comments?
>
> Signed-off-by: Adam Litke <[EMAIL PROTECTED]>
Hrm. I'm always a bit dubious about creating files/directories
starting with '.' during the build. If there are bugs in the make
system anywhere and they don't get cleaned properly, you can spend
ages being mystified as to why things aren't working properly, because
you don't see the bogus . directories in ls normally.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Libhugetlbfs-devel mailing list
Libhugetlbfs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libhugetlbfs-devel
