From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-80795-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 5174 invoked by alias); 4 May 2011 18:13:29 -0000
Received: (qmail 5145 invoked by uid 22791); 4 May 2011 18:13:27 -0000
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0	tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Received: from sibelius.xs4all.nl (HELO glazunov.sibelius.xs4all.nl) (83.163.83.176)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 04 May 2011 18:13:11 +0000
Received: from glazunov.sibelius.xs4all.nl (kettenis@localhost [127.0.0.1])	by glazunov.sibelius.xs4all.nl (8.14.3/8.14.3) with ESMTP id p44IAXk6003640;	Wed, 4 May 2011 20:10:34 +0200 (CEST)
Received: (from kettenis@localhost)	by glazunov.sibelius.xs4all.nl (8.14.3/8.14.3/Submit) id p44IAVlq008135;	Wed, 4 May 2011 20:10:32 +0200 (CEST)
Date: Wed, 04 May 2011 18:13:00 -0000
Message-Id: <201105041810.p44IAVlq008135@glazunov.sibelius.xs4all.nl>
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: janisjo@codesourcery.com
CC: gdb-patches@sourceware.org
In-reply-to: <4DC1910A.8040603@codesourcery.com> (message from Janis Johnson	on Wed, 04 May 2011 10:46:50 -0700)
Subject: Re: [RFA] bailing out of tests with multiple errors or timeouts
References:  <4DC1910A.8040603@codesourcery.com>
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2011-05/txt/msg00106.txt.bz2

> Date: Wed, 04 May 2011 10:46:50 -0700
> From: Janis Johnson <janisjo@codesourcery.com>

> +    timeout {
> +	# A timeout here often indicates more timeouts later in the test.
> +	fail "$test (timeout)"
> +	fail "Remainder of test"
> +	return
> +    }

Often, so not always.  Really the best way to get rid of these is to
fix the underlying problem.