On Fri, 2009-01-30 at 15:56 +0000, Eric B Munson wrote:
> From: Adam Litke <a...@us.ibm.com>
> 
> Now that libhugetlbfs can work with multiple huge page sizes, testing this
> support has become a priority.  The following patch enables automatic testing
> of page sizes that are mounted and have at least one page allocated.  Care is
> taken to assure that only valid combinations are tested.  For example, 32bit
> tests are not run with 16GB pages.  Following the run, a summary of all page
> sizes tested is printed.  The following is some example output of the new
> script:
> 
> ********** TEST SUMMARY
> *                      64K            16M            16G
> *                      32-bit 64-bit  32-bit 64-bit  32-bit 64-bit
> *     Total testcases:    86     89      86     89       0     89
> *             Skipped:    20      0      20      0       0      0
> *                PASS:    59     75      62     85       0     49
> *                FAIL:     5      6       1      1       0     29
> *    Killed by signal:     0      0       0      0       0      0
> *   Bad configuration:     2      2       3      3       0     10
> *       Expected FAIL:     0      0       0      0       0      0
> *     Unexpected PASS:     0      0       0      0       0      0
> * Strange test result:     0      6       0      0       0      1
> **********
> 
> Script programming language conversion alert:
> 
> This patch rewrites run_tests.sh in python.  I already anticipate the "why
> change languages" comments so I come prepared with justification for the
> conversion.  Our test harness has extended beyond simply executing a list of
> test cases and dumping the output to stdout.  The data set for the test 
> summary
> is now three-dimensional.  It is indexed by result type (total tests, total
> passed, etc), word size, and now page size.  The simple arrays in bash are not
> up to the task.  As the number of tests that are run increases, so does the
> challenge of presenting the results in a meaningful, easy to digest format.
> Shell scripts lack the output formatting constructs that are present in
> languages such as Python and that make flexible output formatting possible.
> For these reasons (and the guarantee that the test harness will need to get
> even more sophisticated in the future), I made the inevitable decision to cut
> over to Python now.
> 
> Signed-off-by: Eric B Munson <ebmun...@us.ibm.com>
Signed-off-by: Adam Litke <a...@us.ibm.com>




------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libhugetlbfs-devel mailing list
Libhugetlbfs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libhugetlbfs-devel

Reply via email to