Return-Path: Delivered-To: apmail-httpd-test-dev-archive@www.apache.org Received: (qmail 61716 invoked from network); 5 Mar 2004 02:18:44 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 5 Mar 2004 02:18:44 -0000 Received: (qmail 61627 invoked by uid 500); 5 Mar 2004 02:18:27 -0000 Delivered-To: apmail-httpd-test-dev-archive@httpd.apache.org Received: (qmail 61590 invoked by uid 500); 5 Mar 2004 02:18:27 -0000 Mailing-List: contact test-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: test-dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list test-dev@httpd.apache.org Received: (qmail 61573 invoked from network); 5 Mar 2004 02:18:26 -0000 Received: from unknown (HELO mail.logilune.com) (195.154.174.52) by daedalus.apache.org with SMTP; 5 Mar 2004 02:18:26 -0000 Received: from stason.org (localhost.logilune.com [127.0.0.1]) by mail.logilune.com (Postfix) with ESMTP id 684DF1E17A3 for ; Fri, 5 Mar 2004 03:18:34 +0100 (CET) Message-ID: <4047E379.6030000@stason.org> Date: Thu, 04 Mar 2004 18:18:33 -0800 From: Stas Bekman Organization: Hope, Humanized User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115 X-Accept-Language: en-us, en, he, ru MIME-Version: 1.0 To: test-dev@httpd.apache.org Subject: Re: [A-T patch] give a hint how to raise the timeout References: <4047C6A8.1050007@stason.org> <0D1F4D42-6E3F-11D8-AEF6-000A95972D84@kineticode.com> <4047D35B.1010907@stason.org> <4047DEFF.2090102@stason.org> <8A47C153-6E49-11D8-AEF6-000A95972D84@kineticode.com> In-Reply-To: <8A47C153-6E49-11D8-AEF6-000A95972D84@kineticode.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N David Wheeler wrote: >> Alternatively we could say: >> >> giving up after 121 secs. If you think that your system >> is slow or overloaded try again with a longer timeout value. >> For example set the env var APACHE_TEST_STARTUP_TIMEOUT to a longer >> value, >> e.g. 400 and repeat the last command. >> >> But can we trust the user to know how to set an env var? May be we >> should. > > > Yeah, I think so, though you might want to say "environment variable", > instead. Of course, I was just laze to type it out ;) >> The only reason I mentioned -startup_timeout=420 is that if they have >> already used that option, APACHE_TEST_STARTUP_TIMEOUT won't take an >> effect, since command line options override env vars. But may be they >> will figure it out on their own. > > > Well, you could still say "Or repeat the last command with the > -startup_timeout=420 option". That would work, if the last command was 'make test' or any other wrapper. >> Really, what I'm after is to give users as many hints as possible to >> get their side's problem resolved by themselves before they waste >> their and my time submitting a bug which is not. > > > Of course, it's a good thing to do. I'm just nitpicking the wording. ;-) And thank you for that ;) -- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:stas@stason.org http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com