[PATCH 0/N] test-suite improvement - PASS/FAIL: initial patch

[Jeff Law]

On 09/17/2012 10:05 AM, Siddhesh Poyarekar wrote:
> On Mon, 17 Sep 2012 11:41:36 +0000, Joseph wrote:
>> This doesn't readily give a list of passing tests, though you can get
>> that by using "make --debug=b -k check".  But really the point is so
>> that not everyone needs to reinvent the wheel in such ways - so that
>> you can simply use standard glibc testsuite machinery to give a list
>> of test results.
>
> Agreed, just that I would to have preferred to see something that can
> be built upon to make a standard testsuite of sorts and this approach
> of a file per test doesn't seem the kind of thing that would take our
> testsuite too far.
>
> If a file per test is the only way out, I would be more comfortable
> patching test-skeleton.c to write PASS/FAIL/etc. as the last line of the
> testcase.out file. I know that there are a lot of tests that don't use
> the skeleton and the right thing to do would be to fix those in the
> process.
Do those files outside the test-skeleton framework exit with a usable 
status?  If so we could wrap exit to print the pass/fail message.  IIRC 
this is what the gcc testsuite does under the hood to make life easier 
for remote embedded testing.

Jeff