From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA/doco/testsuite] Document new gdb_test_timeout global variable.
Date: Mon, 08 Feb 2010 12:17:00 -0000 [thread overview]
Message-ID: <1265631452-2476-1-git-send-email-brobecker@adacore.com> (raw)
Hello,
This patch documents a new testsuite variable introduced to allow
the user to configure the timeout duration used while running
the testsuite.
http://www.sourceware.org/ml/gdb-patches/2010-02/msg00101.html
gdb/doc/ChangeLog:
* gdbint.texinfo (Testsuite): New section "Testsuite Configuration",
documenting the gdb_test_timeout variable.
This patch was tested on x86_64-linux by rebuilding the PDF, PS and
HTML documentation.
OK to apply?
Thanks,
--
Joel
---
gdb/doc/gdbint.texinfo | 28 ++++++++++++++++++++++++++++
1 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo
index c90af05..b97d0e1 100644
--- a/gdb/doc/gdbint.texinfo
+++ b/gdb/doc/gdbint.texinfo
@@ -7693,6 +7693,34 @@ make site.exp
runtest TRANSCRIPT=y
@end smallexample
+@section Testsuite Configuration
+
+It is possible to adjust the behavior of the testsuite by defining
+the global variables listed below, either in a @file{site.exp} file,
+or in a @code{board} file.
+
+@itemize @bullet
+
+@item @code{gdb_test_timeout}
+
+Defining this variable changes the default timeout duration used during
+communication with @value{GDBN}. More specifically, the global variable
+used during testing is @code{timeout}, but this variable gets reset to
+@code{gdb_test_timeout} at the beginning of each testcase, making sure
+that any local change to @code{timeout} in a testcase does not affect
+subsequent testcases.
+
+If not specifically defined, this variable gets automatically defined
+to the same value as @code{timeout} during the testsuite initialization
+(the actual value depends on the exact running parameters).
+
+This global variable is usually used when the debugger is slower than
+normal due to the testing environment, triggering unexpected @code{TIMEOUT}
+test failures. For instance, when testing on a remote machine, or against
+a system where communications are slow.
+
+@end itemize
+
@section Testsuite Organization
@cindex test suite organization
--
1.6.3.3
next reply other threads:[~2010-02-08 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 12:17 Joel Brobecker [this message]
2010-02-08 18:24 ` Eli Zaretskii
2010-02-09 13:10 ` Joel Brobecker
2010-02-09 18:44 ` Eli Zaretskii
2010-02-11 7:52 ` Joel Brobecker
2010-02-11 18:43 ` Eli Zaretskii
2010-02-12 4:49 ` Joel Brobecker
2010-02-12 10:05 ` Eli Zaretskii
2010-02-13 4:57 ` Joel Brobecker
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=1265631452-2476-1-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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