From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>, Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH] [gdb/testsuite] Wait longer for core generation
Date: Wed, 30 Nov 2022 14:25:40 -0700 [thread overview]
Message-ID: <87mt88m8x7.fsf@tromey.com> (raw)
In-Reply-To: <20221130145830.1535-1-tdevries@suse.de> (Tom de Vries via Gdb-patches's message of "Wed, 30 Nov 2022 15:58:30 +0100")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> When I run the gdb testsuite on a powerpc64le-linux system with (slow) nfs
Tom> file system, I run into timeouts due to core generation, like for instance:
Tom> ...
Tom> (gdb) gcore $outputs/gdb.ada/task_switch_in_core/crash.gcore^M
Tom> FAIL: gdb.ada/task_switch_in_core.exp: save a corefile (timeout)
Tom> ...
Tom> Fix this by using with_timeout_factor 3 in gdb_gcore_cmd.
Tom> Tested on powerpc64le-linux.
This seems fine to me.
Tom
prev parent reply other threads:[~2022-11-30 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 14:58 Tom de Vries
2022-11-30 21:25 ` Tom Tromey [this message]
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=87mt88m8x7.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).