You are viewing a plain text version of this content. The canonical link for it is here.

Posted to modperl@perl.apache.org by Maurice Yarrow <ya...@best.com> on 2006/06/04 09:38:21 UTC

mod_perl make test failed tests

Hello mod_perl community

Environment:
FC1,
apache2.0.58,
perl5.8.8,
mod_perl2.0.2.

I am getting some failed tests during the "make test" for mod_perl 2.0.2,
in particular:

Failed Test                      Stat Wstat Total Fail  Failed  List of 
Failed
-------------------------------------------------------------------------------
t/apache/content_length_header.t               27    1   3.70%  17
t/api/status.t                                  6    2  33.33%  4-5

I am aware that there are some current postings concerning this issue.  
So I
proceeded to

  % cd mod_perl-2.0.2
  % t/TEST -clean
  % t/TEST -verbose compat/apache_util.t modperl/pnotes.t


which reported

  All tests successful.
  Files=2, Tests=23,  1 wallclock secs ( 0.68 cusr +  0.04 csys =  0.72 CPU)
  [warning] server localhost.localdomain:8529 shutdown

Question:
Is the resulting mod_perl usable?   Or is it to be considered untrustworthy?

(I will send the detailed test reports, if you request them, but since 
this seems
to be a known issue, I presumed, correctly, I hope, that the above would be
sufficient.)

Regards, and thanks
Maurice Yarrow

Re: mod_perl make test failed tests

Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.

On Mon, 5 Jun 2006, Tyler MacDonald wrote:

> Lionel MARTIN <ma...@hotmail.com> wrote:
>> To be honest, I'm running Apache, mod_perl and DBI under Win32 (+Mason) and
>> I can't complain about it.
>>
>> I'd like to test and compare with LAMP to see what's the best (in term of
>> speed and memory managament), but what you told me made me jump, thinking
>> "Am I doing a mistake when targetting to use Win32 on a production server?"
>>
>> Let me have your conclusuions if you can,
>
> 	I would never run a public server where I did not have the ability
> to inspect the source code that it ran on. I think that is a lot like
> driving a car where you can not pop open the hood, or drinking a can of pop
> that does not have a list of ingredients on it.

There's more appropriate forums for continuing that
line of discussion :)

As for what's best to use in a production server, there's 
lots of choices, of course - you could look at LAMP,
although some would recommend FreeBSD for heavy network
traffic. A lot depends on your hardware, the anticipated
level of usage, whether most pages are expected to be
static or dynamic, etc. etc.

The great strides made with Apache/2.x on Windows
make it viable for use as a production server (which
many people do). The question about threads is
a bit academic here, as Apache uses it in their
mpm_winnt module for Windows, which was designed
from scratch and is optimized for use on Win32.
Similarly, ActivePerl 8xx (based on perl-5.8) has
made great gains, especially regarding thread
handling. So, especially if there's other reasons
for using Windows (eg, availability of other
applications), running Apache/Perl/... on Win32
these days is probably a legitimate option.

-- 
best regards,
Randy Kobes