From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 56271 invoked by alias); 17 Jun 2016 11:27:08 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 55634 invoked by uid 89); 17 Jun 2016 11:27:07 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mx1.redhat.com Subject: Re: [PATCH] Add compile testing to glibc test framework. To: Joseph Myers References: <575679A0.4090209@redhat.com> Cc: "Carlos O'Donell" , GNU C Library From: Florian Weimer Message-ID: <5f651b7e-de54-3207-2a15-81e0ba1aea41@redhat.com> Date: Fri, 17 Jun 2016 11:27:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2016-06/txt/msg00654.txt.bz2 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. Florian