This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [2.20] [1/6] Generate .test-result files for ordinary tests
- From: Brooks Moses <bmoses at google dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: libc-alpha <libc-alpha at sourceware dot org>
- Date: Mon, 10 Feb 2014 15:45:45 -0800
- Subject: Re: [2.20] [1/6] Generate .test-result files for ordinary tests
- Authentication-results: sourceware.org; auth=none
- References: <Pine dot LNX dot 4 dot 64 dot 1401100208000 dot 9412 at digraph dot polyomino dot org dot uk> <Pine dot LNX dot 4 dot 64 dot 1401100210220 dot 9412 at digraph dot polyomino dot org dot uk> <52F94F49 dot 9040902 at google dot com> <Pine dot LNX dot 4 dot 64 dot 1402102323520 dot 26591 at digraph dot polyomino dot org dot uk>
On Mon, Feb 10, 2014 at 3:24 PM, Joseph S. Myers
<joseph@codesourcery.com> wrote:
> On Mon, 10 Feb 2014, Brooks Moses wrote:
>> Would there be any utility in recording the values of the nonzero exit codes
>> somewhere?
>
> Where? Not on the PASS/FAIL lines, as the text after "PASS: " or "FAIL: "
> is not meant to depend on the result of the test, to facilitate
> comparison.
You could put it in the .test-result file in a way that is discarded
when these files are accumulated into the per-directory summary files
-- for instance, you could put it on a second line and only accumulate
the first lines.
For that matter, much of the information in the .test-result file
seems redundant; the $test_name (aside from the directory) is also
encoded in the name of the file itself, the directory is known when
the files are accumulated, and the pass/fail status is all that
remains. So that suggests that one option is to replace the
.test-result file with a .test-exit-code file that only contains the
exit code (and an xfail notation if relevant), and for the
accumulation script to convert that into PASS/FAIL tags. That may be
a bit extreme, though.
- Brooks