This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Add compile testing to glibc test framework.
- From: Carlos O'Donell <carlos at redhat dot com>
- To: Florian Weimer <fweimer at redhat dot com>, Joseph Myers <joseph at codesourcery dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 17 Jun 2016 09:51:12 -0400
- Subject: Re: [PATCH] Add compile testing to glibc test framework.
- Authentication-results: sourceware.org; auth=none
- References: <575679A0 dot 4090209 at redhat dot com> <alpine dot DEB dot 2 dot 20 dot 1606071725500 dot 10967 at digraph dot polyomino dot org dot uk> <5f651b7e-de54-3207-2a15-81e0ba1aea41 at redhat dot com>
On 06/17/2016 07:27 AM, Florian Weimer wrote:
> On 06/07/2016 07:28 PM, Joseph Myers wrote:
>> On Tue, 7 Jun 2016, Carlos O'Donell wrote:
>>
>>> Previously these kinds of tests would result in the testsuite
>>> failing to run to completion because compiler errors are treated
>>> as harness failures.
>>
>> I don't actually see this as a problem - that is, I don't see why
>> any compile failure should be hard to fix for some system-specific
>> reason. I'd rather just add such tests as normal tests, that break
>> the build if they fail.
>
> What's annoying with that is that you lose test summary reporting.
> If this was somehow fixed (without impacting make running times,
> please), I think there wouldn't much of an incentive to add such
> compile-time testing.
What would you like fixed? Summary reporting of failed compile
and link?
That's an interesting solution, wrap the compiles and link with
something like evaluate-test.sh but designed to capture failed
compiles and failed links and report them properly as a new
kind of failed test code?
--
Cheers,
Carlos.