From dev-return-7462-apmail-stdcxx-dev-archive=stdcxx.apache.org@stdcxx.apache.org Fri Apr 25 21:33:34 2008 Return-Path: Delivered-To: apmail-stdcxx-dev-archive@www.apache.org Received: (qmail 93780 invoked from network); 25 Apr 2008 21:33:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Apr 2008 21:33:34 -0000 Received: (qmail 91751 invoked by uid 500); 25 Apr 2008 21:33:35 -0000 Delivered-To: apmail-stdcxx-dev-archive@stdcxx.apache.org Received: (qmail 91737 invoked by uid 500); 25 Apr 2008 21:33:35 -0000 Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stdcxx.apache.org Delivered-To: mailing list dev@stdcxx.apache.org Received: (qmail 91726 invoked by uid 99); 25 Apr 2008 21:33:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Apr 2008 14:33:35 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.30.140.160] (HELO moroha.roguewave.com) (208.30.140.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Apr 2008 21:32:43 +0000 Received: from exchmail01.Blue.Roguewave.Com (exchmail01.blue.roguewave.com [10.22.129.22]) by moroha.roguewave.com (8.13.6/8.13.6) with ESMTP id m3PLX2Kt005291 for ; Fri, 25 Apr 2008 21:33:02 GMT X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: Regression tests file structure Date: Fri, 25 Apr 2008 15:32:39 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Regression tests file structure Thread-Index: AcinBzak/3SspE5qTcO0QfuNdtOLRAAE3/Kg References: <48122AE1.1060805@roguewave.com> From: "Eric Lemings" To: X-Virus-Checked: Checked by ClamAV on apache.org =20 > -----Original Message----- > From: Martin Sebor [mailto:sebor@roguewave.com]=20 > Sent: Friday, April 25, 2008 1:03 PM > To: dev@stdcxx.apache.org > Subject: Re: Regression tests file structure >=20 > Eric Lemings wrote: > > =20 > > Not that it really matters but I noticed lots of rather=20 > small programs > > for the regression tests. Couldn't these be consolidated into fewer > > source files, by component perhaps, with a function for=20 > each individual > > regression test? Just a thought. >=20 > I'm sure they could, and it would probably benefit our build > times. The problem is that a severe failure in one of them > (build or runtime) would cause the rest of them to fail too. > Getting around it would require non-trivial changes to our > build harness (e.g., build each test into a separate object > file, linking them all together into a single executable, > and on a runtime failure in one re-link all those that > didn't get to run into a new executable, and repeat). Mmm, that's not quite what I had in mind. Here's an example of what I had in mind: test/regress/21.string.cpp: ... static void test_stdcxx_162 () { ... } static void test_stdcxx_231 () { ... } static void test_stdcxx_466 () { ... } static void run_tests () { test_stdcxx_162 (); test_stdcxx_231 (); test_stdcxx_466 (); } All regression tests related to the same component (i.e. clause) are contained in the same source file. That wouldn't require build/test harness changes, would it? And yes a build or run failure would cause them all to fail but I'd see that as real incentive for correcting the failure. :) Brad.