public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/28870] [4.2/4.3/4.4 Regression] configuring, over-riding timeout values in testsuite Date: Tue, 18 Nov 2008 22:49:00 -0000 [thread overview] Message-ID: <20081118224812.6094.qmail@sourceware.org> (raw) In-Reply-To: <bug-28870-365@http.gcc.gnu.org/bugzilla/> ------- Comment #21 from janis at gcc dot gnu dot org 2008-11-18 22:48 ------- Interesting that you should ask, I modified the patch yesterday and intend to submit it as soon as I've done some more testing. The current version adds dg-timeout, which sets the timeout for running the compiler in gcc and libstdc++ tests to a specified number of seconds, or dg-timeout-factor, which multiplies the usual timeout by the specified factor. The "usual timeout" is the value for the target board, which can be overridden by gcc_timeout or v3_timeout defined in $HOME/.dejagnurc. Let me know if you've got suggestions for improvement. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28870
next prev parent reply other threads:[~2008-11-18 22:49 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-08-28 12:29 [Bug testsuite/28870] New: " bkoz at gcc dot gnu dot org 2006-08-31 2:53 ` [Bug testsuite/28870] [4.2 Regression] " pinskia at gcc dot gnu dot org 2006-09-01 22:12 ` mmitchel at gcc dot gnu dot org 2006-09-12 16:36 ` sje at cup dot hp dot com 2006-09-12 23:23 ` janis at gcc dot gnu dot org 2006-09-12 23:42 ` janis at gcc dot gnu dot org 2006-09-13 6:26 ` bkoz at gcc dot gnu dot org 2006-09-13 16:54 ` janis at gcc dot gnu dot org 2006-09-21 21:10 ` bkoz at gcc dot gnu dot org 2006-10-09 21:45 ` bkoz at gcc dot gnu dot org 2006-11-28 9:18 ` [Bug testsuite/28870] [4.2/4.3 " christian dot joensson at gmail dot com 2007-02-07 10:10 ` hp at gcc dot gnu dot org 2007-02-07 10:12 ` hp at gcc dot gnu dot org 2007-02-07 10:16 ` hp at gcc dot gnu dot org 2007-05-14 21:28 ` mmitchel at gcc dot gnu dot org 2007-07-20 3:47 ` mmitchel at gcc dot gnu dot org 2007-10-09 19:27 ` mmitchel at gcc dot gnu dot org 2007-10-23 17:39 ` janis at gcc dot gnu dot org 2007-10-23 17:39 ` janis at gcc dot gnu dot org 2007-11-17 12:19 ` rask at gcc dot gnu dot org 2008-02-01 16:59 ` jsm28 at gcc dot gnu dot org 2008-04-06 16:04 ` [Bug testsuite/28870] [4.2/4.3/4.4 " nightstrike at gmail dot com 2008-05-19 20:32 ` jsm28 at gcc dot gnu dot org 2008-11-18 22:41 ` sje at cup dot hp dot com 2008-11-18 22:49 ` janis at gcc dot gnu dot org [this message] 2008-11-18 23:22 ` sje at cup dot hp dot com 2008-11-21 0:59 ` janis at gcc dot gnu dot org 2008-11-21 1:29 ` janis at gcc dot gnu dot org 2008-11-24 22:33 ` janis at gcc dot gnu dot org 2008-11-26 18:53 ` janis at gcc dot gnu dot org 2008-11-26 22:17 ` janis at gcc dot gnu dot org 2008-12-02 17:47 ` janis at gcc dot gnu dot org 2008-12-02 17:50 ` janis at gcc dot gnu dot org
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=20081118224812.6094.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).