You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by "Kinyon, Rob" <Ro...@progressive-medical.com> on 2004/03/25 15:36:22 UTC

Testing issues w/ mod_perl 1.99_13

I have two testing issues with MP2. The first is using both _12 and _13
and the second is specific to _13.

I am on Sparc/Solaris9, using Perl 5.8.0, Apache 2.0.49, and openssl
0.9.7d. If you need versions of other stuff, please ask.

1) I have compiled Apache2 with a very restricted set of options. (My
theory is that if I don't need it, I don't want it.) The configure line
I used (for Apache2.0.48 and 2.0.49) is:
./configure --enable-ssl --enable-proxy --disable-actions --disable-asis
--disable-autoindex --disable-dir --disable-imap --disable-negotiation
--disable-status --disable-userdir --with-ssl=/usr/local/ssl
--disable-ipv6

I'm having problems in that some of the tests in _12 and _13 use
RewriteEngine, which I have disabled. To get _12 to pass, I had to
delete all mention of "RewriteEngine".

2) _13 compiled fine using 2.0.49. However, it will not pass the tests.
I removed all mention of RewriteEngine, but still ran into problems. The
error log has no errors in it. The only item is that it seems to have
MaxClients set to 1.

-------- BEGIN TEST OUTPUT --------
server localhost:8529 started
server localhost:8530 listening (TestVhost::config)
server localhost:8531 listening (TestModperl::merge)
server localhost:8532 listening (TestModperl::perl_options)
server localhost:8533 listening (TestModperl::setupenv)
server localhost:8534 listening (TestProtocol::echo_filter)
server localhost:8535 listening (TestProtocol::echo)
server localhost:8536 listening (TestPreConnection::note)
server localhost:8537 listening (TestHooks::stacked_handlers2)
server localhost:8538 listening (TestHooks::startup)
server localhost:8539 listening (TestFilter::in_bbs_inject_header)
server localhost:8540 listening (TestFilter::in_str_msg)
server localhost:8541 listening (TestFilter::both_str_con_add)
server localhost:8542 listening (TestFilter::in_bbs_msg)
server localhost:8543 listening (TestDirective::perlmodule)
server localhost:8544 listening (TestDirective::perlrequire)
server localhost:8545 listening (TestPerl::ithreads)
server localhost:8546 listening (TestDirective::perlloadmodule4)
server localhost:8547 listening (TestDirective::perlloadmodule5)
server localhost:8548 listening (TestDirective::perlloadmodule3)
server localhost:8549 listening (TestDirective::perlloadmodule6)
t/apr-ext/uuid...............1..3
Can't load
'/export/home/rob/distros/mod_perl-1.99_13/blib/arch/auto/APR/APR.so'
for module APR: ld.so.1: /usr/local/bin/perl: fatal: libiconv.so.2: open
failed: No such file or directory at
/usr/local/lib/perl5/5.8.0/sun4-solaris/DynaLoader.pm line 229.
 at t/apr-ext/uuid.t line 25
Compilation failed in require at t/apr-ext/uuid.t line 25.
dubious
        Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 1-3
        Failed 3/3 tests, 0.00% okay
t/filter/both_str_con_add....1..4
ok 1
# expected: mod_perl
# received: 
not ok 2
# Failed test 2 in t/filter/both_str_con_add.t at line 22
# expected: 2.0
# received: 
not ok 3
# Failed test 3 in t/filter/both_str_con_add.t at line 22 fail #2
# expected: rules
# received: 
not ok 4
# Failed test 4 in t/filter/both_str_con_add.t at line 22 fail #3
FAILED tests 2-4
        Failed 3/4 tests, 25.00% okay
t/protocol/echo..............1..3
ok 1
Use of uninitialized value in chomp at t/protocol/echo.t line 18.
dubious
        Test returned status 22 (wstat 5632, 0x1600)
DIED. FAILED tests 2-3
        Failed 2/3 tests, 33.33% okay
t/protocol/echo_filter.......1..3
ok 1
Use of uninitialized value in chomp at t/protocol/echo_filter.t line 18.
dubious
        Test returned status 22 (wstat 5632, 0x1600)
DIED. FAILED tests 2-3
        Failed 2/3 tests, 33.33% okay
Failed Test                 Stat Wstat Total Fail  Failed  List of
Failed
------------------------------------------------------------------------
-------
t/apr-ext/uuid.t             255 65280     3    3 100.00%  1-3
t/filter/both_str_con_add.t                4    3  75.00%  2-4
t/protocol/echo.t             22  5632     3    2  66.67%  2-3
t/protocol/echo_filter.t      22  5632     3    2  66.67%  2-3
[warning] server localhost:8529 shutdown
[  error] error running tests (please examine t/logs/error_log)
-------- END TEST OUTPUT --------

Doing an ls -l on /usr/local/lib/*icon* gives the following:
rob@dev01 $ ls -l /usr/local/lib/*icon*
-rw-r--r--   1 bin      cvs          749 Jan 26  2003
/usr/local/lib/libiconv.la
lrwxrwxrwx   1 root     other         17 Dec 19 09:20
/usr/local/lib/libiconv.so -> libiconv.so.2.1.0*
lrwxrwxrwx   1 root     other         17 Dec 19 09:20
/usr/local/lib/libiconv.so.2 -> libiconv.so.2.1.0*
-rwxr-xr-x   1 bin      cvs      1139112 Jan 26  2003
/usr/local/lib/libiconv.so.2.1.0*
-rw-r--r--   1 bin      cvs      1140436 Jan 26  2003
/usr/local/lib/libiconv_plug.so

As a minor nit, the ulimit command (to allow core files) doesn't work on
Solaris9 bash.

Thanks,
Rob Kinyon

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: [Apache-Test] ulimit on Solaris bash

Posted by Stas Bekman <st...@stason.org>.
Stas Bekman wrote:
> Kinyon, Rob wrote:
> 
>>> As a minor nit, the ulimit command (to allow core files) doesn't work on
>>> Solaris9 bash.
> 
> 
>> so how does it inhibit during 'make test'? and what is the right thing 
>> to do to allow core files on your bash?

Kinyon, Rob wrote:

 > As for ulimit ... You're right - I had the wrong command. I googled a
 > little and found something useful at
 > http://perl.apache.org/docs/2.0/devel/debug/c.html#Obtaining_core_Files_
 > under_Solaris
 > which discusses Solaris8, but looks to be relevant to my situation.
 >
 > The reason I brought the error up is that when I run "ulimit -c
 > unlimited", I receive the following error: "bash: ulimit: cannot modify
 > limit: Not owner". I found a bug report dating back to 1997 on the
 > topic, but could find no follow-ups or further information.

Is that something common to Solaris 8, or is it specific to the bash 
installation that you have? i.e. could it be that other bash versions do 
accept it? If it's the same I suppose we need to skip that state for Solaris 
8. Please show the code to indentify Solaris 8 ($^O + %Config) and I will add it.

__________________________________________________________________
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

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: [Apache-Test] ulimit on Solaris bash

Posted by Stas Bekman <st...@stason.org>.
Kinyon, Rob wrote:

> As a minor nit, the ulimit command (to allow core files) doesn't work on
> Solaris9 bash.

so how does it inhibit during 'make test'? and what is the right thing to do 
to allow core files on your bash?

__________________________________________________________________
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

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: Testing issues w/ mod_perl 1.99_13

Posted by Stas Bekman <st...@stason.org>.
Stas Bekman wrote:
> Kinyon, Rob wrote:
> 
> Rob, please submit a properl bug report: http://perl.apache.org/bugs/

You can't be bothered to help us resolve your problems? :(

__________________________________________________________________
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

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: Testing issues w/ mod_perl 1.99_13

Posted by Stas Bekman <st...@stason.org>.
Kinyon, Rob wrote:

Rob, please submit a properl bug report: http://perl.apache.org/bugs/

> 2) _13 compiled fine using 2.0.49. However, it will not pass the tests.
> I removed all mention of RewriteEngine, but still ran into problems. The
> error log has no errors in it. The only item is that it seems to have
> MaxClients set to 1.

it should be 2, can you should us the relevant section from httpd.conf? on my 
machine (guessing that you are running prefork) it's:

<IfModule prefork.c>
     StartServers         1
     MaxClients           2
     MaxRequestsPerChild  0
</IfModule>

I suppose you are talking about MaxClients limit reaching, which you can 
safely ignore in the test suite.

> t/filter/both_str_con_add....1..4
> ok 1
> # expected: mod_perl
> # received: 
> not ok 2
> # Failed test 2 in t/filter/both_str_con_add.t at line 22
> # expected: 2.0
> # received: 
> not ok 3
> # Failed test 3 in t/filter/both_str_con_add.t at line 22 fail #2
> # expected: rules
> # received: 
> not ok 4
> # Failed test 4 in t/filter/both_str_con_add.t at line 22 fail #3
> FAILED tests 2-4
>         Failed 3/4 tests, 25.00% okay
> t/protocol/echo..............1..3
> ok 1
> Use of uninitialized value in chomp at t/protocol/echo.t line 18.
> dubious
>         Test returned status 22 (wstat 5632, 0x1600)
> DIED. FAILED tests 2-3
>         Failed 2/3 tests, 33.33% okay
> t/protocol/echo_filter.......1..3
> ok 1
> Use of uninitialized value in chomp at t/protocol/echo_filter.t line 18.
> dubious
>         Test returned status 22 (wstat 5632, 0x1600)
> DIED. FAILED tests 2-3
>         Failed 2/3 tests, 33.33% okay
> Failed Test                 Stat Wstat Total Fail  Failed  List of
> Failed
> ------------------------------------------------------------------------
> -------

> t/filter/both_str_con_add.t                4    3  75.00%  2-4
> t/protocol/echo.t             22  5632     3    2  66.67%  2-3
> t/protocol/echo_filter.t      22  5632     3    2  66.67%  2-3

Interesting, all 3 test have one thing in common - they use a raw socket to 
communicate with the client.  So this is probably something that doesn't work 
on your machine. Are there known socket problems in perl on your platform?

__________________________________________________________________
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

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: Testing issues w/ mod_perl 1.99_13

Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
> 
>>+        <IfModule mod_rewrite.c>
> 
> 
>>+            RewriteEngine On
> 
> 
> actually, rewrite seems to be a leftover, maybe from when the test was being
> originally written - I can't see the need for rewrite at all and removing
> the RewriteEngine directive still allows the tests to pass (as you mentioned).
> 
> but let's let stas look at it just to be sure (he wrote it originally).

Sounds right to me, Geoff.

__________________________________________________________________
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

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: Testing issues w/ mod_perl 1.99_13

Posted by Geoffrey Young <ge...@modperlcookbook.org>.

> +        <IfModule mod_rewrite.c>

> +            RewriteEngine On

actually, rewrite seems to be a leftover, maybe from when the test was being
originally written - I can't see the need for rewrite at all and removing
the RewriteEngine directive still allows the tests to pass (as you mentioned).

but let's let stas look at it just to be sure (he wrote it originally).

--Geoff


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Re: Testing issues w/ mod_perl 1.99_13

Posted by Geoffrey Young <ge...@modperlcookbook.org>.

Geoffrey Young wrote:
>>I'm having problems in that some of the tests in _12 and _13 use
>>RewriteEngine, which I have disabled. To get _12 to pass, I had to
>>delete all mention of "RewriteEngine".
> 
> 
> please try the attached patch.

oops, sorry - I forgot to change one thing.  please discard the last patch
and try this instead.

--Geoff

Re: Testing issues w/ mod_perl 1.99_13

Posted by Geoffrey Young <ge...@modperlcookbook.org>.
> I'm having problems in that some of the tests in _12 and _13 use
> RewriteEngine, which I have disabled. To get _12 to pass, I had to
> delete all mention of "RewriteEngine".

please try the attached patch.

--Geoff