You are viewing a plain text version of this content. The canonical link for it is here.
Posted to test-dev@perl.apache.org by "Philip M. Gollucci" <pg...@p6m7g8.com> on 2006/11/10 07:58:53 UTC
Re: [RELEASE CANDIDATE] libapreq2 2.09-RC2
Issac Goldstand wrote:
> Following up on the FAIL report for win32:
Can you post your "configuration" steps -- I'm the wrong person to ask,
but someone else might know. I see Steve H. got passing results.
Which CGI tests fail ?
> The new Apache-Test-1.29-RC2 runs the test suite for 2.08 just fine
> (against mod_perl-2.0.3-RC2). However, here the test suite can't load
> mod_perl (also mod_perl-2.0.3-RC2) into the server properly:
The dection of mod_perl has changed 0 between 1.27->1.29 much less
1.29-rc1 and 1.29-rc2
> CGI passes most tests (it fails 7; libapreq-2.08 also fails the same
> ones lately. That's a separate issue for a separate thread, though),
> it's just the mod_perl ones that seem to fail.
Didn't you just contradict yourself ? I'm probably reading that wrong
>
> Deeper probing (t/conf/httpd.conf) shows that:
> <IfModule !mod_perl.c>
> #unable to locate mod_perl.so (could be a static build)
> </IfModule>
Yes that would be the problem. (does Apache-Test have the correct path
to apxs and is it actually functional?)
> Giving a path via t/TEST -libmodperl didn't help
Unfortunately, httpd-apreq unlike mod_perl does not yet handle this flag.
> Fixing the path to mod_perl manually in t/conf/httpd.conf did fix it
> (and all tests but the same 7 from CGI passed).
D'oh!
--
------------------------------------------------------------------------
Philip M. Gollucci (pgollucci@p6m7g8.com) 323.219.4708
Consultant / http://p6m7g8.net/Resume/resume.shtml
Senior Software Engineer - TicketMaster - http://ticketmaster.com
1024D/A79997FA F357 0FDD 2301 6296 690F 6A47 D55A 7172 A799 97F
I never had a dream come true
'Til the day that I found you.
Even though I pretend that I've moved on
You'll always be my baby.
I never found the words to say
You're the one I think about each day
And I know no matter where life takes me to
A part of me will always be...
A part of me will always be with you.
Re: [RELEASE CANDIDATE] libapreq2 2.09-RC2
Posted by Issac Goldstand <ma...@beamartyr.net>.
OK.
New fresh builds of Perl 5.8.8, Apache 2.2.3, randy's apxs, mod_perl
2.0.3-rc2, Apache::Test-1.29-rc2, in their own clean tree, using VC6
(and Windows SDK just for building apache, for the ldap stuff)
So far so good. mod_perl was detected by Apache-Test this time (so I
guess we'll never know why it broke for me last week, since the PC I had
it on is now FUBAR)
But the 7 CGI tests still break for me
The tests numbers are 32, 36-41 (in 2.09-rc2), and they all generate 500
errors
I've uploaded the HTTP streams for any masochists (I really don't think
there's anything in there more useful than the 500 error, but maybe
someone will do me the favor of proving me wrong) to
http://www.beamartyr.net/apreq-cgi.xml.bz2
I still say +1 to roll 2.09, since no one else seems to get these
errors. Hopefully I'll figure out why I can't seem to get rid of them
and fix anything needing fixing in 2.10
Issac
Re: [RELEASE CANDIDATE] libapreq2 2.09-RC2
Posted by Issac Goldstand <ma...@beamartyr.net>.
Randy Kobes wrote:
> On Fri, 10 Nov 2006, Issac Goldstand wrote:
>
>> Philip M. Gollucci wrote:
>>> Issac Goldstand wrote:
>>>> Following up on the FAIL report for win32:
>>
>>> Which CGI tests fail ?
>>
>> Erm, my win32 build computer fizzled a bit last night, but I'll try to
>> remember to post this on Sunday. I've already seen the same tests
>> failing on a separate PC with a separate build environment (at work -
>> yesterday's build were on my home office PC); I saw it when I was
>> originally writing the interactive-cgi module (but never found time to
>> chase them down)
>>
>>>
>>>> The new Apache-Test-1.29-RC2 runs the test suite for 2.08 just fine
>>>> (against mod_perl-2.0.3-RC2). However, here the test suite can't load
>>>> mod_perl (also mod_perl-2.0.3-RC2) into the server properly:
>>> The dection of mod_perl has changed 0 between 1.27->1.29 much less
>>> 1.29-rc1 and 1.29-rc2
>>>
>>>> CGI passes most tests (it fails 7; libapreq-2.08 also fails the same
>>>> ones lately. That's a separate issue for a separate thread, though),
>>>> it's just the mod_perl ones that seem to fail.
>>> Didn't you just contradict yourself ? I'm probably reading that wrong
>>>
>>
>> I don't think so - the CGI (t/apreq/cgi.t) test runs as a normal CGI, so
>> IIRC doesn't go through mod_perl...
>
> That's true, but it needs mod_perl, for some APR::* modules.
Not quite; it needs the perl glue (eg, the XS extensions linked against
APR/Apache)
It doesn't need Apache running mod_perl.so
> Can you try installing the latest mod_perl-2.0.3-rc2 that
> Philip posted to see if that helps?
>
That's what I was using.
>>>> Deeper probing (t/conf/httpd.conf) shows that:
>>>> <IfModule !mod_perl.c>
>>>> #unable to locate mod_perl.so (could be a static build)
>>>> </IfModule>
>>> Yes that would be the problem. (does Apache-Test have the correct path
>>> to apxs and is it actually functional?)
>>>
>>
>> I believe so; the same Apache-Test detects the same mod_perl just fine
>> on the 2.08 tarball - it's really quite odd... Sunday I'll see if I can
>> reproduce this at work.
>
> Does the installed Apache::TestConfigData point to the
> correct httpd.exe?
>
Not sure - trying to replicate this at work now - we'll see what happens.
Issac
Re: [RELEASE CANDIDATE] libapreq2 2.09-RC2
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Fri, 10 Nov 2006, Issac Goldstand wrote:
> Philip M. Gollucci wrote:
>> Issac Goldstand wrote:
>>> Following up on the FAIL report for win32:
>
>> Which CGI tests fail ?
>
> Erm, my win32 build computer fizzled a bit last night, but I'll try to
> remember to post this on Sunday. I've already seen the same tests
> failing on a separate PC with a separate build environment (at work -
> yesterday's build were on my home office PC); I saw it when I was
> originally writing the interactive-cgi module (but never found time to
> chase them down)
>
>>
>>> The new Apache-Test-1.29-RC2 runs the test suite for 2.08 just fine
>>> (against mod_perl-2.0.3-RC2). However, here the test suite can't load
>>> mod_perl (also mod_perl-2.0.3-RC2) into the server properly:
>> The dection of mod_perl has changed 0 between 1.27->1.29 much less
>> 1.29-rc1 and 1.29-rc2
>>
>>> CGI passes most tests (it fails 7; libapreq-2.08 also fails the same
>>> ones lately. That's a separate issue for a separate thread, though),
>>> it's just the mod_perl ones that seem to fail.
>> Didn't you just contradict yourself ? I'm probably reading that wrong
>>
>
> I don't think so - the CGI (t/apreq/cgi.t) test runs as a normal CGI, so
> IIRC doesn't go through mod_perl...
That's true, but it needs mod_perl, for some APR::* modules.
Can you try installing the latest mod_perl-2.0.3-rc2 that
Philip posted to see if that helps?
>>> Deeper probing (t/conf/httpd.conf) shows that:
>>> <IfModule !mod_perl.c>
>>> #unable to locate mod_perl.so (could be a static build)
>>> </IfModule>
>> Yes that would be the problem. (does Apache-Test have the correct path
>> to apxs and is it actually functional?)
>>
>
> I believe so; the same Apache-Test detects the same mod_perl just fine
> on the 2.08 tarball - it's really quite odd... Sunday I'll see if I can
> reproduce this at work.
Does the installed Apache::TestConfigData point to the
correct httpd.exe?
--
best regards,
Randy Kobes
Re: [RELEASE CANDIDATE] libapreq2 2.09-RC2
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Fri, 10 Nov 2006, Issac Goldstand wrote:
> Philip M. Gollucci wrote:
>> Issac Goldstand wrote:
>>> Following up on the FAIL report for win32:
>
>> Which CGI tests fail ?
>
> Erm, my win32 build computer fizzled a bit last night, but I'll try to
> remember to post this on Sunday. I've already seen the same tests
> failing on a separate PC with a separate build environment (at work -
> yesterday's build were on my home office PC); I saw it when I was
> originally writing the interactive-cgi module (but never found time to
> chase them down)
>
>>
>>> The new Apache-Test-1.29-RC2 runs the test suite for 2.08 just fine
>>> (against mod_perl-2.0.3-RC2). However, here the test suite can't load
>>> mod_perl (also mod_perl-2.0.3-RC2) into the server properly:
>> The dection of mod_perl has changed 0 between 1.27->1.29 much less
>> 1.29-rc1 and 1.29-rc2
>>
>>> CGI passes most tests (it fails 7; libapreq-2.08 also fails the same
>>> ones lately. That's a separate issue for a separate thread, though),
>>> it's just the mod_perl ones that seem to fail.
>> Didn't you just contradict yourself ? I'm probably reading that wrong
>>
>
> I don't think so - the CGI (t/apreq/cgi.t) test runs as a normal CGI, so
> IIRC doesn't go through mod_perl...
That's true, but it needs mod_perl, for some APR::* modules.
Can you try installing the latest mod_perl-2.0.3-rc2 that
Philip posted to see if that helps?
>>> Deeper probing (t/conf/httpd.conf) shows that:
>>> <IfModule !mod_perl.c>
>>> #unable to locate mod_perl.so (could be a static build)
>>> </IfModule>
>> Yes that would be the problem. (does Apache-Test have the correct path
>> to apxs and is it actually functional?)
>>
>
> I believe so; the same Apache-Test detects the same mod_perl just fine
> on the 2.08 tarball - it's really quite odd... Sunday I'll see if I can
> reproduce this at work.
Does the installed Apache::TestConfigData point to the
correct httpd.exe?
--
best regards,
Randy Kobes
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [RELEASE CANDIDATE] libapreq2 2.09-RC2
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Fri, 10 Nov 2006, Issac Goldstand wrote:
> Philip M. Gollucci wrote:
>> Issac Goldstand wrote:
>>> Following up on the FAIL report for win32:
>
>> Which CGI tests fail ?
>
> Erm, my win32 build computer fizzled a bit last night, but I'll try to
> remember to post this on Sunday. I've already seen the same tests
> failing on a separate PC with a separate build environment (at work -
> yesterday's build were on my home office PC); I saw it when I was
> originally writing the interactive-cgi module (but never found time to
> chase them down)
>
>>
>>> The new Apache-Test-1.29-RC2 runs the test suite for 2.08 just fine
>>> (against mod_perl-2.0.3-RC2). However, here the test suite can't load
>>> mod_perl (also mod_perl-2.0.3-RC2) into the server properly:
>> The dection of mod_perl has changed 0 between 1.27->1.29 much less
>> 1.29-rc1 and 1.29-rc2
>>
>>> CGI passes most tests (it fails 7; libapreq-2.08 also fails the same
>>> ones lately. That's a separate issue for a separate thread, though),
>>> it's just the mod_perl ones that seem to fail.
>> Didn't you just contradict yourself ? I'm probably reading that wrong
>>
>
> I don't think so - the CGI (t/apreq/cgi.t) test runs as a normal CGI, so
> IIRC doesn't go through mod_perl...
That's true, but it needs mod_perl, for some APR::* modules.
Can you try installing the latest mod_perl-2.0.3-rc2 that
Philip posted to see if that helps?
>>> Deeper probing (t/conf/httpd.conf) shows that:
>>> <IfModule !mod_perl.c>
>>> #unable to locate mod_perl.so (could be a static build)
>>> </IfModule>
>> Yes that would be the problem. (does Apache-Test have the correct path
>> to apxs and is it actually functional?)
>>
>
> I believe so; the same Apache-Test detects the same mod_perl just fine
> on the 2.08 tarball - it's really quite odd... Sunday I'll see if I can
> reproduce this at work.
Does the installed Apache::TestConfigData point to the
correct httpd.exe?
--
best regards,
Randy Kobes
Re: [RELEASE CANDIDATE] libapreq2 2.09-RC2
Posted by Issac Goldstand <ma...@beamartyr.net>.
Philip M. Gollucci wrote:
> Issac Goldstand wrote:
>> Following up on the FAIL report for win32:
> Can you post your "configuration" steps -- I'm the wrong person to ask,
> but someone else might know. I see Steve H. got passing results.
>
Just perl Makefile.PL, nmake, nmake test
> Which CGI tests fail ?
Erm, my win32 build computer fizzled a bit last night, but I'll try to
remember to post this on Sunday. I've already seen the same tests
failing on a separate PC with a separate build environment (at work -
yesterday's build were on my home office PC); I saw it when I was
originally writing the interactive-cgi module (but never found time to
chase them down)
>
>> The new Apache-Test-1.29-RC2 runs the test suite for 2.08 just fine
>> (against mod_perl-2.0.3-RC2). However, here the test suite can't load
>> mod_perl (also mod_perl-2.0.3-RC2) into the server properly:
> The dection of mod_perl has changed 0 between 1.27->1.29 much less
> 1.29-rc1 and 1.29-rc2
>
>> CGI passes most tests (it fails 7; libapreq-2.08 also fails the same
>> ones lately. That's a separate issue for a separate thread, though),
>> it's just the mod_perl ones that seem to fail.
> Didn't you just contradict yourself ? I'm probably reading that wrong
>
I don't think so - the CGI (t/apreq/cgi.t) test runs as a normal CGI, so
IIRC doesn't go through mod_perl...
>>
>> Deeper probing (t/conf/httpd.conf) shows that:
>> <IfModule !mod_perl.c>
>> #unable to locate mod_perl.so (could be a static build)
>> </IfModule>
> Yes that would be the problem. (does Apache-Test have the correct path
> to apxs and is it actually functional?)
>
I believe so; the same Apache-Test detects the same mod_perl just fine
on the 2.08 tarball - it's really quite odd... Sunday I'll see if I can
reproduce this at work.
>> Giving a path via t/TEST -libmodperl didn't help
> Unfortunately, httpd-apreq unlike mod_perl does not yet handle this flag.
>
>> Fixing the path to mod_perl manually in t/conf/httpd.conf did fix it
>> (and all tests but the same 7 from CGI passed).
> D'oh!
>
>