Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stdcxx.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: STDCXX-536
Date: Fri, 7 Mar 2008 12:13:07 -0700
Message-ID: 
 <CFFDD219128FD94FB4F92B99F52D0A49010A3632@exchmail01.Blue.Roguewave.Com>
Thread-Topic: STDCXX-536
Thread-Index: AciAh0X/M+ftad1yTGKx0bTJevyVmA==
From: "Eric Lemings" <Eric.Lemings@roguewave.com>
To: <dev@stdcxx.apache.org>


FWIW, I was just reading the description for Jira issue STDCXX-536 and
the associated comments.
=20
I believe this is basically what Travis has already stated in a round-
about manner but it seems to me that if a test is timing out, there are
two possibilities: 1. the test is caught in an infinite loop, or 2.)
the test requires too much time to completely execute.  In either case,
the test needs to be rewritten to fix the infinite loop or to break
the test into smaller tests that can completely execute in a reasonably
short amount of time -- a couple of minutes at most on the slowest
supported platforms.

And aren't multithreaded programs (or tests) supposed to perform faster
-- not slower -- than their single-threaded counterparts?  :)
=20
Brad.