From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23748 invoked by alias); 26 Feb 2008 15:55:26 -0000 Received: (qmail 23729 invoked by uid 22791); 26 Feb 2008 15:55:23 -0000 X-Spam-Check-By: sourceware.org Received: from mu-out-0910.google.com (HELO mu-out-0910.google.com) (209.85.134.189) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 26 Feb 2008 15:55:06 +0000 Received: by mu-out-0910.google.com with SMTP id g7so4128207muf.0 for ; Tue, 26 Feb 2008 07:55:03 -0800 (PST) Received: by 10.82.155.10 with SMTP id c10mr9262657bue.29.1204041303341; Tue, 26 Feb 2008 07:55:03 -0800 (PST) Received: by 10.82.162.12 with HTTP; Tue, 26 Feb 2008 07:55:03 -0800 (PST) Message-ID: <8f2776cb0802260755q7c48c3d9me8d35807c3d35ae7@mail.gmail.com> Date: Tue, 26 Feb 2008 16:02:00 -0000 From: "Jim Blandy" To: "Maciej W. Rozycki" Subject: Re: testsuite: Of all the timeouts provided always select the largest Cc: gdb-patches@sourceware.org, "Maciej W. Rozycki" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: 6fd1e3f62cec7614 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-02/txt/msg00389.txt.bz2 I've often thought that what would be coolest would be for gdb_expect to accept a factor to be applied to the ambient timeout, rather than a new absolute number of seconds. After all, the only thing a specific use of gdb_expect knows is that the response it's waiting for will take longer (or shorter?) than usual to arrive; it doesn't know anything about the absolute performance of the system under test.