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 2002/03/12 17:50:31 UTC
raising maxclients in mod_perl test suites
Doug, is there any special reason why we have only one server running
for mod_perl tests? I need to raise it to at least two, since I need to
test the fetch of the scoreboard image, which requires two parallel
requests.
diff -u -r1.4 TestRunPerl.pm
--- Apache-Test/lib/Apache/TestRunPerl.pm 31 Dec 2001 08:39:48 -0000
1.4
+++ Apache-Test/lib/Apache/TestRunPerl.pm 12 Mar 2002 16:47:06 -0000
@@ -23,6 +23,16 @@
configure_startup_pl));
}
+# subclass new_test_config to add some config vars which will be
+# replaced in generated httpd.conf
+sub new_test_config {
+ my $self = shift;
+
+ $self->{conf_opts}->{maxclients} = 2;
+
+ return $self->SUPER::new_test_config;
+}
+
sub configure {
my $self = shift;
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: raising maxclients in mod_perl test suites
Posted by Stas Bekman <st...@stason.org>.
Doug MacEachern wrote:
> On Wed, 13 Mar 2002, Stas Bekman wrote:
>
>
>>Doug, is there any special reason why we have only one server running
>>for mod_perl tests?
>>
>
> same reason as 1.x, to run all tests in the same process == better chance
> of hitting bugs. 1.x also did it to test interpreter state, but we have
> the same_interp routines for that now. personally, i would prefer to keep
> that as the default, have the scoreboard tests check maxclients to see if
> that test can run. you can run 't/TEST -maxclients 2' to raise it. we
> can think about changing the default to 2 later, but in any case would
> want 't/TEST -maxclients 1' to work, so scoreboard tests should have the
> logic either way.
OK, will do it in that way. Thanks!
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: raising maxclients in mod_perl test suites
Posted by Doug MacEachern <do...@covalent.net>.
On Wed, 13 Mar 2002, Stas Bekman wrote:
> Doug, is there any special reason why we have only one server running
> for mod_perl tests?
same reason as 1.x, to run all tests in the same process == better chance
of hitting bugs. 1.x also did it to test interpreter state, but we have
the same_interp routines for that now. personally, i would prefer to keep
that as the default, have the scoreboard tests check maxclients to see if
that test can run. you can run 't/TEST -maxclients 2' to raise it. we
can think about changing the default to 2 later, but in any case would
want 't/TEST -maxclients 1' to work, so scoreboard tests should have the
logic either way.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org