From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Simon Marchi <simon.marchi@efficios.com>,
Tom Tromey <tom@tromey.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Increase timeout in gdb.mi/list-thread-groups-available.exp
Date: Fri, 02 Aug 2019 13:43:00 -0000 [thread overview]
Message-ID: <87tvazisy8.fsf@tromey.com> (raw)
In-Reply-To: <cba4616c-4e3c-4217-7c7a-40fb576ea351@suse.de> (Tom de Vries's message of "Fri, 2 Aug 2019 08:39:14 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> for me, both tests fail with a timeout. And if we're increasing the
Tom> timeout, how about we only do that if check-read1 is used?
I'm reluctant to make the test suite more sensitive to the environment
it's running it. Is the reason to do this that the test can time out
normally, and so we'd like to avoid lengthy timeouts? If that's the
case, can the test be fixed somehow instead?
I guess my mental model here is that a timeout should not matter unless
a test is flaky. But maybe that's naive? I don't know :-)
Tom> +proc with_timeout_factor { factor body {body_uplevel 1}} {
I think body_uplevel shouldn't be needed.
Tom> + return [with_timeout_factor $factor $body 2]
... since this can just do
return [uplevel [list with_timeout_factor $factor $body]]
thanks,
Tom
next prev parent reply other threads:[~2019-08-02 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 14:39 Simon Marchi
2019-08-01 18:18 ` Tom Tromey
2019-08-01 19:16 ` Simon Marchi
[not found] ` <cba4616c-4e3c-4217-7c7a-40fb576ea351@suse.de>
2019-08-02 13:43 ` Tom Tromey [this message]
2019-08-02 14:46 ` Simon Marchi
2019-08-05 13:58 ` Tom de Vries
2019-08-05 14:23 ` Simon Marchi
2019-08-05 13:53 ` Tom de Vries
2019-08-15 17:58 ` Pedro Alves
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=87tvazisy8.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
--cc=tdevries@suse.de \
/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