You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by Stas Bekman <st...@stason.org> on 2003/11/05 20:43:16 UTC
controlling the timeout of server start in Apache-Test
The thing that triggered my recent post about the ridiculously slow perl_clone
is that my smoke tests almost always fail to run the worker mpm, if my machine
is busy running some other heavy tasks at the same moment. 60 secs is just not
enough to start the worker server's test suite under utilized CPU (with an
absolutely free CPU it takes about 30 secs to start). I'm not sure we want to
keep on changing the hardcoded limit of 60 secs, I was thinking maybe to add a
new option which I can use to test worker mpm builds.
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: controlling the timeout of server start in Apache-Test
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
>
> FYI: Geoff added -startup_timeout || $ENV{APACHE_TEST_STARTUP_TIMEOUT}
whoops - forgot those commits don't go here :)
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: controlling the timeout of server start in Apache-Test
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>
>
> Stas Bekman wrote:
>
>> The thing that triggered my recent post about the ridiculously slow
>> perl_clone is that my smoke tests almost always fail to run the worker
>> mpm, if my machine is busy running some other heavy tasks at the same
>> moment. 60 secs is just not enough to start the worker server's test
>> suite under utilized CPU (with an absolutely free CPU it takes about
>> 30 secs to start). I'm not sure we want to keep on changing the
>> hardcoded limit of 60 secs, I was thinking maybe to add a new option
>> which I can use to test worker mpm builds.
>
>
> I suppose we can add a new command-line flag, but an environment
> variable would probably be more useful.
>
> I'll work on that today.
FYI: Geoff added -startup_timeout || $ENV{APACHE_TEST_STARTUP_TIMEOUT}
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: controlling the timeout of server start in Apache-Test
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
Stas Bekman wrote:
> The thing that triggered my recent post about the ridiculously slow
> perl_clone is that my smoke tests almost always fail to run the worker
> mpm, if my machine is busy running some other heavy tasks at the same
> moment. 60 secs is just not enough to start the worker server's test
> suite under utilized CPU (with an absolutely free CPU it takes about 30
> secs to start). I'm not sure we want to keep on changing the hardcoded
> limit of 60 secs, I was thinking maybe to add a new option which I can
> use to test worker mpm builds.
I suppose we can add a new command-line flag, but an environment variable
would probably be more useful.
I'll work on that today.
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org