Stas,

It's been awhile, but I'm back to working on these tests under FreeBSD
5.3 with mp2. I'm using the current release (2.0.0) with Apache 2.0.54.
The root of many of my problems appears to be how Apache is resolving my
localhost address. Apparently FBSD resolves localhost to my Jail IP.
Apache is expecting the more usual 127.0.0.1. I was able to resolve the
issues reported below by adding the following line to my /etc/hosts file
above all other definitions:

  192.168.1.1 localhost

Assuming my jail ip was 192.168.1.1 this works and most tests are now
pasing. Thanks for bearing with me while I came to an understanding
about the behavior of localhost within a jail.

Currently, I'm still having troubles with t/filter/both_str_con_add.t.
Here's the output:

  t/filter/both_str_con_add....1..4
  # Running under perl version 5.008006 for freebsd
  # Current time local: Thu Jun  2 05:03:50 2005
  # Current time GMT:   Thu Jun  2 09:03:50 2005
  # Using Test.pm version 1.25
  # Using Apache/Test.pm version 1.25
  ok 1
  # expected: mod_perl
  # received: mod_perl
  # Failed test 3 in t/filter/both_str_con_add.t at line 25 fail #2
  # Failed test 4 in t/filter/both_str_con_add.t at line 25 fail #3
  ok 2
  # expected: 2.0
  # received:
  not ok 3
  # expected: rules
  # received:
  not ok 4
  FAILED tests 3-4

As well as t/protocol/echo_block.t with the following output:

  t/protocol/echo_block....1..3
  # Running under perl version 5.008006 for freebsd
  # Current time local: Thu Jun  2 06:31:17 2005
  # Current time GMT:   Thu Jun  2 10:31:17 2005
  # Using Test.pm version 1.25
  # Using Apache/Test.pm version 1.25
  ok 1
  # expected: hello
  # received: hello
  ok 2
  # Failed test 3 in t/protocol/echo_block.t at line 22 fail #2
  # expected: world
  # received:
  not ok 3
  FAILED test 3
          Failed 1/3 tests, 66.67% okay

In both cases, the first string works but the following ones are
failing. My guess is that the culprit is 

    my $socket = Apache::TestRequest::vhost_socket

which is used across all three of the failing tests. I'll try to spend
some more time on it later today.

Also, the t/protocol/echo_filter.t test is failing. It runs tests 1 and
2 then keeps running until it fills up the disk space then dumps a
massive core file. I'm just skipping it for now.


William


On Fri, Feb 18, 2005 at 05:32:49PM -0500, Stas Bekman wrote:
> William McKee wrote:
> [...]
> >To recap, these are the results of the mp2 test (RC4) with the following
> >environment setting:
> >
> >  export ac_cv_o_nonblock_inherited=yes
> [...]
> >  # Failed test 2 in t/api/access2.t at line 15
> >  # testing : no credentials passed
> >  # expected: 401
> >  # received: 403
> >  not ok 2
> 
> I'm not sure why this happens. It should be:
> 
> # testing : no credentials passed
> # expected: 401
> # received: 401
> ok 2
> 
> HTTP_FORBIDDEN is not returned by ap_get_basic_auth_pw. Try to dump the 
> $rc code in that sub-test in t/response/TestAPI/access2.pm
> 
>     my($rc, $sent_pw) = $r->get_basic_auth_pw;
>     warn "RC: $rc\n";
>     return $rc if $rc != Apache::OK;
> 
> >  ok 3
> >  ok 4
> >  not ok 5
> >  # Failed test 5 in t/api/access2.t at line 24
> >  not ok 6
> >  # Failed test 6 in t/api/access2.t at line 27
> >  FAILED tests 2, 5-6
> 
> What the error_log says about those two?
> 
> It looks like a fileperms problem again. Try to make sure that the 
> ownership of all files under t/ is the same.
> 
> find t -type d -exec chmod u+rwx {} \;
> find t -type f -exec chmod u+rw {} \;
> find t -type d -exec chown uid.gid {} \;
> find t -type f -exec chown uid.gid {} \;
> 
> where uid.gid is the id you use to run the tests with (e.g. nobody.nobody)
> 
> 
> -- 
> __________________________________________________________________
> Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
> http://stason.org/     mod_perl Guide ---> http://perl.apache.org
> mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org   http://ticketmaster.com

-- 
Knowmad Services Inc.
http://www.knowmad.com

Reply via email to