This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[2.20] [0/6] Generate test summaries with PASS / FAIL status


This patch series, intended for after 2.19 has branched, makes the
glibc testsuite generate explicit PASS or FAIL status for individual
glibc tests, with parts loosely based on Tomas Dohnalek's patch
<https://sourceware.org/ml/libc-alpha/2012-10/msg00278.html>.  This
version of the series has a minimal set of patches to achieve the
desired feature, and subsequent versions may well include further
patches with other related cleanups.

The overall strategy is to generate .test-result files when each test
is run, then to collect those together for each subdirectory and then
the whole testsuite to produce a summary of test results.  Patch 6
moves the testsuite to a more conventional approach where plain "make
check" does not terminate for an individual test failure, unless you
say "make stop-on-test-failure=y check"; the previous patches leave
the existing practice (of terminating on failure) unchanged, and the
overall summary will not be generated when the testsuite terminates on
failure, only if a whole run completes.

The testing for each patch includes verifying that it does not change
the set of .out files generated, and that it does not change the set
of .test-result files except where the patch is intended to add such
files for more tests, as evidence that the set of tests that get run
is unchanged.

-- 
Joseph S. Myers
joseph@codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]