Philippe, when you are committing the static build code, please commit
the following patch as well, thanks!
Index: README
===
RCS file: /home/cvs/modperl-2.0/README,v
retrieving revision 1.20
diff -u -r1.20 README
--- README 1 J
Randy Kobes wrote:
On Thu, 8 Jul 2004, Stas Bekman wrote:
Randy Kobes wrote:
[ ... ]
That's great! Does this mean also that the
protocol/echo_bbs2 test passes for you? A few days
ago it was crashing on me, but I haven't tested that
particular test yet with the current cvs.
Nothing has changed s
On Thu, 8 Jul 2004, Stas Bekman wrote:
> Randy Kobes wrote:
[ ... ]
> > That's great! Does this mean also that the
> > protocol/echo_bbs2 test passes for you? A few days
> > ago it was crashing on me, but I haven't tested that
> > particular test yet with the current cvs.
>
> Nothing has chang
Randy Kobes wrote:
On Thu, 8 Jul 2004, Steve Hay wrote:
[ ... ]
I now have all tests successful in the main test suite and
ModPerl-Registry's.
Hi Steve,
That's great! Does this mean also that the
protocol/echo_bbs2 test passes for you? A few days
ago it was crashing on me, but I haven't tested
On Thu, 8 Jul 2004, Steve Hay wrote:
[ ... ]
> I now have all tests successful in the main test suite and
> ModPerl-Registry's.
Hi Steve,
That's great! Does this mean also that the
protocol/echo_bbs2 test passes for you? A few days
ago it was crashing on me, but I haven't tested that
particular
Stas Bekman wrote:
>Steve Hay wrote:
>
>
>>All is not quite well with the current CVS mp2 tests -- the
>>ModPerl-Registry tests fail from t/basic.t onwards.
>>
>>It seems that this test is now crashing Apache.exe. It can be
>>reproduced in isolation. Here's a stack trace:
>>
>>
>[...]
>
Steve Hay wrote:
All is not quite well with the current CVS mp2 tests -- the
ModPerl-Registry tests fail from t/basic.t onwards.
It seems that this test is now crashing Apache.exe. It can be
reproduced in isolation. Here's a stack trace:
[...]
It crashed right at the start of Perl_sv_unmagic()
Randy Kobes wrote:
> On Wed, 7 Jul 2004, Stas Bekman wrote:
>
>
>>Since A-T t_cmp has swapped its args order to submit to other Test::Foo
>>modules conventions, we now have a broken/misleading diagnostics in the
>>verbose testing output, as we get the header 'received:' printed for
>>expected,
Stas Bekman wrote:
>Steve Hay wrote:
>
>
>>Testing out the current CVS mp2, I find that t/perl/ithreads.t outputs a
>>message saying "Scalars leaked: 1" when running the whole test suite:
>>
>>[...]
>>t\perl\api..skipped
>>all skipped: getppid() is not implem
All is not quite well with the current CVS mp2 tests -- the
ModPerl-Registry tests fail from t/basic.t onwards.
It seems that this test is now crashing Apache.exe. It can be
reproduced in isolation. Here's a stack trace:
Perl_sv_unmagic(interpreter * 0x013b237c, sv * 0x, int 99) line
Steve Hay wrote:
Testing out the current CVS mp2, I find that t/perl/ithreads.t outputs a
message saying "Scalars leaked: 1" when running the whole test suite:
[...]
t\perl\api..skipped
all skipped: getppid() is not implemented on Win32
t\perl\hash_attack..
Testing out the current CVS mp2, I find that t/perl/ithreads.t outputs a
message saying "Scalars leaked: 1" when running the whole test suite:
[...]
t\perl\api..skipped
all skipped: getppid() is not implemented on Win32
t\perl\hash_attack..o
I see, that Philippe has found a nice trick to load Apache::PerlSections
at the server startup, w/o actually doing that explicitly. He deployed
the handlers automatic autoloading. Though this trick doesn't work for
other things. I want to move the pre-loading of APR::Error to the the
internals
Stas Bekman wrote:
I can reproduce this with prefork, running:
t/TEST -minclients 1 t/api/slurp_filename.t t/filter/in_error.t
It's now self contained, after I've moved the -T problem eval into
in_error itself:
Index: t/filter/TestFilter/in_error.pm
=
14 matches
Mail list logo
