From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10848 invoked by alias); 21 Sep 2006 21:10:19 -0000 Received: (qmail 10797 invoked by uid 48); 21 Sep 2006 21:10:09 -0000 Date: Thu, 21 Sep 2006 21:10:00 -0000 Message-ID: <20060921211009.10796.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug testsuite/28870] [4.2 Regression] configuring, over-riding timeout values in testsuite In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "bkoz at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-09/txt/msg02108.txt.bz2 List-Id: ------- Comment #7 from bkoz at gcc dot gnu dot org 2006-09-21 21:10 ------- Whoops, Janis, you are right. Sorry for the false alarm. The fancy dejagnu line I spit out at you does nothing. I also tried to hack up this as you suggested: Index: testsuite/lib/libstdc++.exp =================================================================== --- testsuite/lib/libstdc++.exp (revision 117118) +++ testsuite/lib/libstdc++.exp (working copy) @@ -350,8 +350,14 @@ } lappend options "compiler=$cxx_final" - lappend options "timeout=600" + # This is a hack to set the timeout higher. + if [target_info exists gcc,timeout] { + lappend options "timeout=[target_info gcc,timeout]" + } else { + lappend options "timeout=600" + } + return [target_compile $source $dest $type $options] } However, I'm not quite sure how to test that people can over-ride timeout now. Can any testsuite maintainer help please? Just some clear directions on how to do this stuff would be appreciated. -benjamin -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28870