public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r10-9597] libstdc++: Allow dejagnu tool_timeout to be overridden
Date: Mon, 29 Mar 2021 20:03:42 +0000 (GMT)	[thread overview]
Message-ID: <20210329200342.06FCF386EC57@sourceware.org> (raw)

https://gcc.gnu.org/g:f23c816703737d5d8c0d7deb3d0da19bac42619d

commit r10-9597-gf23c816703737d5d8c0d7deb3d0da19bac42619d
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Nov 26 14:42:09 2020 +0000

    libstdc++: Allow dejagnu tool_timeout to be overridden
    
    This allows the default timeout for libstdc++ tests to be set by the
    user, either in ~/.dejagnurc or a site.exp file that $DEJAGNU names.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/lib/libstdc++.exp (libstdc++_init): Only set
            tool_timeout if it hasn't been set by the user already.
    
    (cherry picked from commit 39e837cd7509ca631fdc382128202464063ff56e)

Diff:
---
 libstdc++-v3/testsuite/lib/libstdc++.exp | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/lib/libstdc++.exp b/libstdc++-v3/testsuite/lib/libstdc++.exp
index 16963f2edd5..3b8587cd01d 100644
--- a/libstdc++-v3/testsuite/lib/libstdc++.exp
+++ b/libstdc++-v3/testsuite/lib/libstdc++.exp
@@ -246,7 +246,10 @@ proc libstdc++_init { testfile } {
     }
 
     # Set the default timeout for v3 tests.
-    set tool_timeout 600
+    # You can override this in ~/.dejagnurc or a .exp file named by $DEJAGNU.
+    if {![info exists tool_timeout]} {
+      set tool_timeout 600
+    }
 
     # Default settings.
     set cxx [transform "g++"]


                 reply	other threads:[~2021-03-29 20:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210329200342.06FCF386EC57@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).