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 r11-5574] libstdc++: Reduce default test timeout to 360 seconds
Date: Mon, 30 Nov 2020 14:56:16 +0000 (GMT)	[thread overview]
Message-ID: <20201130145616.AC2DB385802D@sourceware.org> (raw)

https://gcc.gnu.org/g:637800c7bbb222a629076a5d20afda03c2dd1043

commit r11-5574-g637800c7bbb222a629076a5d20afda03c2dd1043
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Nov 30 14:39:54 2020 +0000

    libstdc++: Reduce default test timeout to 360 seconds
    
    The current default of 10 minutes is much longer than most tests need on
    common hardware. The slow tests all now have a dg-timeout-factor
    directive that gives them more time to run relative to the default. The
    default can also be overridden in ~/.dejagnurc or DEJAGNU=site.exp, so
    it seems unnecessary to have such a large default.
    
    This reduces the default from 10 minutes to 6 minutes, which still seems
    more than enough.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/lib/libstdc++.exp (libstdc++_init): Reduce
            default tool_timeout to 360.

Diff:
---
 libstdc++-v3/testsuite/lib/libstdc++.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/lib/libstdc++.exp b/libstdc++-v3/testsuite/lib/libstdc++.exp
index e000dba968f..35817a8870a 100644
--- a/libstdc++-v3/testsuite/lib/libstdc++.exp
+++ b/libstdc++-v3/testsuite/lib/libstdc++.exp
@@ -248,7 +248,7 @@ proc libstdc++_init { testfile } {
     # Set the default timeout for v3 tests.
     # You can override this in ~/.dejagnurc or a .exp file named by $DEJAGNU.
     if {![info exists tool_timeout]} {
-      set tool_timeout 600
+      set tool_timeout 360
     }
 
     # Default settings.


                 reply	other threads:[~2020-11-30 14:56 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=20201130145616.AC2DB385802D@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).