From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 117427 invoked by alias); 7 Jun 2016 17:28:52 -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 117418 invoked by uid 89); 7 Jun 2016 17:28:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=Hx-languages-length:808 X-HELO: relay1.mentorg.com Date: Tue, 07 Jun 2016 17:28:00 -0000 From: Joseph Myers To: Carlos O'Donell CC: GNU C Library Subject: Re: [PATCH] Add compile testing to glibc test framework. In-Reply-To: <575679A0.4090209@redhat.com> Message-ID: References: <575679A0.4090209@redhat.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2016-06/txt/msg00209.txt.bz2 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. > * Rules [ifeq ($(run-built-tests),no)] (tests): Add $(tests-compile). > [ifneq ($(run-built-tests),no)] (tests): Add $(tests-compile:%=$(objpfx)%.out). If .out is compiler output, I see no good reason for this to depend on run-built-tests; such tests should run unconditionally. -- Joseph S. Myers joseph@codesourcery.com