On Wed, 27 Aug 2003, Stas Bekman wrote:
> Randy Kobes wrote:
[ .. ]
> > This has been fixed, and the associated perlio.t test
> > runs on Win32, and passes all but one subtest (I don't have
> > the details handy, but the failure is due to a difference
> > of a single leading space between expe
Randy Kobes wrote:
It's possible that the problem comes from the new PerlIO
Layer, try testing again after disabling it:
[ .. ]
You're right - disabling PERLIO_LAYERS allows the
modules/cgi.t and modules/cgiupload.t to pass ...
I'll try to track down what changes in the past few
weeks led to this
On Wed, 27 Aug 2003, Stas Bekman wrote:
> Stas Bekman wrote:
> > Randy Kobes wrote:
> >> On Wed, 27 Aug 2003, Stas Bekman wrote:
> >>> Randy Kobes wrote:
> On Mon, 25 Aug 2003, Stas Bekman wrote:
> > It's possible that the problem comes from the new PerlIO
> > Layer, try testing again
As mike chamberlain told me over irc, apr-ext/perlio was faling for him
because of the modperl_perl_gensym not being resolved in APR/PerlIO.so. I
didn't see that error since on linux by default symbols resolution is lazy and
since that part of the api wasn't tested I did see the problem. On MacO
Stas Bekman wrote:
Randy Kobes wrote:
On Wed, 27 Aug 2003, Stas Bekman wrote:
Randy Kobes wrote:
On Mon, 25 Aug 2003, Stas Bekman wrote:
It's possible that the problem comes from the new PerlIO
Layer, try testing again after disabling it:
[ .. ]
Hi Stas,
You're right - disabling PERLIO_LA
On Wed, 27 Aug 2003, Stas Bekman wrote:
> Randy Kobes wrote:
> > On Mon, 25 Aug 2003, Stas Bekman wrote:
> >
> >>It's possible that the problem comes from the new PerlIO
> >>Layer, try testing again after disabling it:
> > [ .. ]
> > Hi Stas,
> >You're right - disabling PERLIO_LAYERS allows th
Randy Kobes wrote:
On Wed, 27 Aug 2003, Stas Bekman wrote:
Randy Kobes wrote:
On Mon, 25 Aug 2003, Stas Bekman wrote:
It's possible that the problem comes from the new PerlIO
Layer, try testing again after disabling it:
[ .. ]
Hi Stas,
You're right - disabling PERLIO_LAYERS allows the
module
Geoffrey Young wrote:
this is a pretty big deal, as mod_perl tests have always run against
a single available server. are we sure that this isn't going to be
problematic on some platforms (namely win32, as usual :)? though I
guess from the docs MaxClients is meaningless to that mpm.
Not rea
Randy Kobes wrote:
On Mon, 25 Aug 2003, Stas Bekman wrote:
It's possible that the problem comes from the new PerlIO Layer, try testing
again after disabling it:
[ .. ]
Hi Stas,
You're right - disabling PERLIO_LAYERS allows the
modules/cgi.t and modules/cgiupload.t to pass ...
I'll try to track
I'm glad (OK, I've spent half a day on this) I haven't followed the
suggestion in Bricolage docs to use Apache 1.3.27, but went with
Apache 1.3.28. Today I stepped on the same issue like you have and I
have found the cause of it.
> I just ran into some very strange issues with connections to a
>
On Mon, 25 Aug 2003, Stas Bekman wrote:
> It's possible that the problem comes from the new PerlIO Layer, try testing
> again after disabling it:
[ .. ]
Hi Stas,
You're right - disabling PERLIO_LAYERS allows the
modules/cgi.t and modules/cgiupload.t to pass ...
I'll try to track down what chang
this is a pretty big deal, as mod_perl tests have always run against a
single available server. are we sure that this isn't going to be
problematic on some platforms (namely win32, as usual :)? though I
guess from the docs MaxClients is meaningless to that mpm.
Not really, all tests designe
Stas Bekman wrote:
[EMAIL PROTECTED] wrote:
stas2003/08/26 21:42:38
Modified:t/filter in_str_consume.t
t/filter/TestFilter in_str_consume.pm
Log:
rewrite the input streaming consume filter to bring it up-to-date
with the
latest httpds. make it more elaborate
hi all...
this patch contains only the tests for subrequests used in filters. you
can use it to test or reproduce the problem.
craig - in case it got lost in the mass of email yesterday, if you could
try the latest cvs version of mod_perl and see if it core dumps, that would
be great. re
[EMAIL PROTECTED] wrote:
stas2003/08/26 21:42:38
Modified:t/filter in_str_consume.t
t/filter/TestFilter in_str_consume.pm
Log:
rewrite the input streaming consume filter to bring it up-to-date with the
latest httpds. make it more elaborate at the same time.
Geoff
Stas Bekman wrote:
Nothing has changed with regards to Apache::Test in the last few days.
Purhaps you had a borked checkout.
Negative, ghostrider! Make test fails as before. I just
ignored make test, and installed it anyway, and it
works.
-
Geoffrey Young wrote:
[EMAIL PROTECTED] wrote:
stas2003/08/26 16:28:04
Modified:lib/ModPerl TestRun.pm
Added: t/modules proxy.t
t/response/TestModules proxy.pm
Log:
new test: converting a normal request to a proxy request
- requires to bump up the numb
Geoffrey Young wrote:
[...]
as I said, nowhere in any of the module shipped with core do I find
logic like this - mod_include and mod_cgi both seem to call
ap_run_sub_req without flushing the main data stream (though
mod_include does split the stream and send the data _prior to the tag_
off).
Geoffrey Young wrote:
the problem is with the r->main logic in mpxs_ap_run_sub_req.
with that logic, what ends up happening is that the data currently
being operated on is explicity flushed. this is bad within a
(streaming) filter where you are expected to call $f->print yourself,
as the dat
however, removing that logic causes api/lookup_uri2.t to fail, but I
suspect this is an issue with puts() rather than the subrequest
mechanism - changing puts() to print() makes everything work just
fine. does puts() write directly to the wire, bypassing filters?
Sorry, but that's cheating ;)
Geoffrey Young wrote:
Stas Bekman wrote:
Craig Shelley wrote:
I'll take a look at it. But you didn't supply a complete bug report
as explained http://perl.apache.org/bugs/. Please do so.
I think I've got this figured out.
the problem is with the r->main logic in mpxs_ap_run_sub_req.
with t
[EMAIL PROTECTED] wrote:
stas2003/08/26 16:28:04
Modified:lib/ModPerl TestRun.pm
Added: t/modules proxy.t
t/response/TestModules proxy.pm
Log:
new test: converting a normal request to a proxy request
- requires to bump up the number of maxclients to 2
t
Carl Brewer wrote:
Have you tried gozer's patch? I posted the URL in the previous followup.
I'll try it tonight, and if I have no luck, may have time
to roll my own fix. mod_perl shouldn't care if localhost
is 127.0.0.1 or ::1 in the least, it should make no
difference, IMO :)
It's Apache::Test
Stas Bekman wrote:
So it's an issue with httpd.conf over IPv6.
I'd say so.
Have you tried gozer's patch? I posted the URL in the previous followup.
I'll try it tonight, and if I have no luck, may have time
to roll my own fix. mod_perl shouldn't care if localhost
is 127.0.0.1 or ::1 in the least
Stas Bekman wrote:
May be. I don't have IPv6 here, so I haven't tested with it. Anybody
with IPv6 can help us here? Philippe, when is your patch going in?
Carl, can you test without IPv6 enabled? Or is it too much of a trouble?
Turning off IPv6 on the box is not an option :)
If you install th
Carl Brewer wrote:
Stas Bekman wrote:
Nothing has changed with regards to Apache::Test in the last few days.
Purhaps you had a borked checkout.
Negative, ghostrider! Make test fails as before. I just
ignored make test, and installed it anyway, and it
works.
So it's an issue with httpd.conf o
Carl Brewer wrote:
Stas Bekman wrote:
May be. I don't have IPv6 here, so I haven't tested with it. Anybody
with IPv6 can help us here? Philippe, when is your patch going in?
Carl, can you test without IPv6 enabled? Or is it too much of a trouble?
If you install things nevertheless can you run
Carl Brewer wrote:
Stas Bekman wrote:
May be. I don't have IPv6 here, so I haven't tested with it. Anybody
with IPv6 can help us here? Philippe, when is your patch going in?
Carl, can you test without IPv6 enabled? Or is it too much of a trouble?
Turning off IPv6 on the box is not an option :
Stas Bekman wrote:
May be. I don't have IPv6 here, so I haven't tested with it. Anybody
with IPv6 can help us here? Philippe, when is your patch going in?
Carl, can you test without IPv6 enabled? Or is it too much of a trouble?
If you install things nevertheless can you run your own things off
29 matches
Mail list logo
