From: "Jim Blandy" <jimb@red-bean.com>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: gdb-patches@sourceware.org, "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: testsuite: Of all the timeouts provided always select the largest
Date: Tue, 26 Feb 2008 16:02:00 -0000 [thread overview]
Message-ID: <8f2776cb0802260755q7c48c3d9me8d35807c3d35ae7@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0802251311540.28703@perivale.mips.com>
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.
next prev parent reply other threads:[~2008-02-26 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 15:55 Maciej W. Rozycki
2008-02-26 16:02 ` Jim Blandy [this message]
2008-02-26 16:17 ` Maciej W. Rozycki
2008-02-26 16:39 ` Jim Blandy
2008-02-27 15:43 ` Maciej W. Rozycki
2008-02-27 15:45 ` Daniel Jacobowitz
2008-02-26 16:10 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f2776cb0802260755q7c48c3d9me8d35807c3d35ae7@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=macro@mips.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox