runtest always produces a summary output file
`tool.sum'. This summary shows the names of all test files
run; for each test file, one line of output from each
command (showing status `PASS' or `XPASS') or
command (status `FAIL' or `XFAIL'); trailing summary
statistics that count passing and failing tests (expected and
unexpected); and the full pathname and version number of the tool
tested. (All possible outcomes, and all errors, are always reflected in
the summary output file, regardless of whether or not you specify
If any of your tests use the procedures
untested, the summary output also
tabulates the corresponding outcomes.
For example, after `runtest --tool binutils', look for a summary
log in `binutils.sum'. Normally,
runtest writes this file
in your current working directory; use the `--outdir' option to
select a different directory.
Here is a short sample summary log:
Test Run By rob on Mon May 25 21:40:57 PDT 1992 === gdb tests === Running ./gdb.t00/echo.exp ... PASS: Echo test Running ./gdb.all/help.exp ... PASS: help add-symbol-file PASS: help aliases PASS: help breakpoint "bre" abbreviation FAIL: help run "r" abbreviation Running ./gdb.t10/crossload.exp ... PASS: m68k-elf (elf-big) explicit format; loaded XFAIL: mips-ecoff (ecoff-bigmips) "ptype v_signed_char" signed C types === gdb Summary === # of expected passes 5 # of expected failures 1 # of unexpected failures 1 /usr/latest/bin/gdb version 4.6.5 -q
Go to the first, previous, next, last section, table of contents.