perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ODELL, TODD E \(SWBT\)" <to2...@sbc.com>
Subject RE: ModPerl 2.0.1 AIX4.3.3 - Make Test Fails to run
Date Wed, 17 Aug 2005 20:59:13 GMT
Thanks for the quick reply. I just realized that even when I run export
APACHE_TEST_STARTUP_TIMEOUT=420 ( or any other value) it uses the
default 300. Shouldn't the command export
APACHE_TEST_STARTUP_TIMEOUT=420 set it for the test?
I edited the ModPerl::TestRun from 300 to 600 to see if that would be
better but got the same results. So far, regardless of the TIMEOUT value
it will fail on waiting for server to start though for the first 10
seconds I can see the httpd running under ps -ef but it never gets past
the 
[Wed Aug 17 13:53:56 2005] [info] base server + 27 vhosts
Line. And seems to exit without writing to the error_log.

What confuses me as well is if I manually run the command:
/apacheDev/bin/httpd  -d /home/to2958/mod_perl-2.0.1/t -f
/home/to2958/mod_perl-2.0.1/t/conf/httpd.conf -D APACHE2 -D
PERL_USEITHREADS
I see this:
[Wed Aug 17 15:04:22 2005] [info] 6 Apache2:: modules loaded
[Wed Aug 17 15:04:22 2005] [info] 0 APR:: modules loaded
[Wed Aug 17 15:04:22 2005] [info] base server + 27 vhosts ready to run
tests
And then it exits and in total it's taking only ~10 seconds to complete.
But it only prints something like this to the error_log:
END in modperl_extra.pl, pid=39342

I'll try shutting other programs down prior to running and see if I can
set the timeout higher. I'm a little dubious

Is there another why to run this to show more detail of what's going on?


Thanks
-----Original Message-----
From: Philip M. Gollucci [mailto:pgollucci@p6m7g8.com] 
Sent: Wednesday, August 17, 2005 12:42 PM
To: ODELL, TODD E (SWBT)
Cc: modperl@perl.apache.org
Subject: Re: ModPerl 2.0.1 AIX4.3.3 - Make Test Fails to run


ODELL, TODD E (SWBT) wrote:
> to start. I unpacked and compiled as my userid, not root, and am able
to
> start the httpd directly as that userid. With the
> APACHE_TEST_STARTUP_TIMEOUT=420 this is what is get from make test:
I believe whats happening here is that because you are testing the 
threaded version, you computer its taking too long to load and start all

the tests.  The ModPerl-Registry tests load substantially less; thus, 
start quicker.  You might try stopping other processes on your computer 
while make testing if it is busy.

If I read that correctly, 300s is not enough, but 420 is?

 From

lib/ModPerl/TestRun.pm:
sub new_test_config {
     my $self = shift;

     # default timeout in secs (threaded mpms are extremely slow to
     # startup, due to a slow perl_clone operation)
     $self->{conf_opts}->{startup_timeout} ||=
         $ENV{APACHE_TEST_STARTUP_TIMEOUT} ||
         Apache2::Build->build_config->mpm_is_threaded() ? 300 : 120;

     $self->{conf_opts}->{minclients} ||= MIN_CLIENTS;

     ModPerl::TestConfig->new($self->{conf_opts});
}
> *** /usr/opt/perl5.8.6/bin/perl -V
> Summary of my perl5 (revision 5 version 8 subversion 6) configuration:
>     usethreads=define use5005threads=undef useithreads=define
> usemultiplicity=define

> Characteristics of this binary (from libperl): 
>   Compile-time options: MULTIPLICITY USE_ITHREADS USE_LARGE_FILES
> PERL_IMPLICIT_CONTEXT

> Apache2            : -
> Apache2::Request   : 2.05-dev
Since you seem to be uptodate with most things, libapreq-2.06-dev is out
and fixes a few things :)



-- 
END
------------------------------------------------------------
     What doesn't kill us can only make us stronger.
                 Nothing is impossible.
				
Philip M. Gollucci (pgollucci@p6m7g8.com) 301.254.5198
Consultant / http://p6m7g8.net/Resume/
Senior Developer / Liquidity Services, Inc.
   http://www.liquidityservicesinc.com
        http://www.liquidation.com
        http://www.uksurplus.com
        http://www.govliquidation.com
        http://www.gowholesale.com


Mime
View raw message