You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by Stas Bekman <st...@stason.org> on 2004/08/13 18:19:01 UTC
time for 1.99_15?
Yesterday I've fixed the problems that were showstoppers for the _15
release. Any objections for doing it in the next few days?
If there are none, any volunteers to do this release?
We could get an RC right now, let it cook over the weekend and if
everything goes well release on Monday?
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>
> Stas Bekman wrote:
>
>>Yesterday I've fixed the problems that were showstoppers for the _15
>>release. Any objections for doing it in the next few days?
>>
>>If there are none, any volunteers to do this release?
>>
>>We could get an RC right now, let it cook over the weekend and if
>>everything goes well release on Monday?
>
>
> in general I don't think much testing gets done over the weekend, so if
> you're serious about getting candidate results better to let it sit until
> tuesday so that people can test on monday (as the EU people have gone to the
> pub already today).
OK, so let's post RC on Sunday/Monday then. We don't want to have the
code frozen for too long. I'm planning to work over this weekend.
> other than that +1 (and I guess that answers my A-T question as well :)
Yup :)
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Subject: [mp2] make test fails
Posted by Jie Gao <J....@isu.usyd.edu.au>.
On Tue, 17 Aug 2004, Stas Bekman wrote:
> Date: Tue, 17 Aug 2004 23:56:48 -0700
> From: Stas Bekman <st...@stason.org>
> To: Jie Gao <J....@isu.usyd.edu.au>
> Cc: mod_perl Dev <de...@perl.apache.org>
> Subject: Re: time for 1.99_15?
>
> Jie Gao wrote:
> > Hi Stas,
> >
> > perl-5.8.3_threaded + Latest cvs + apache_2.0.49
> > ------------------------------------------------
> >
> > make test fails with the error:
> >
> > ....
> > [warning] testing whether 'nobody' is able to -rwx /u0/local/src/modperl-2.0/t
> > "/usr/local/perl-5.8.3_threaded/bin/perl" -Mlib=/u0/local/src/modperl-2.0/Apache-Test/lib -MApache::TestRun -e
> > 'eval { Apache::TestRun::run_root_fs_test(60001, 60001, q[/u0/local/src/modperl-2.0/t]) }';
> >
> >
> > [warning] result: OK
> > [warning] the client side drops 'root' permissions and becomes 'nobody'
> > /usr/local/apache_2.0.49/bin/httpd -d /u0/local/src/modperl-2.0/t -f /u0/local/src/modperl-2.0/t/conf/httpd.conf
> > -D APACHE2 -D PERL_USEITHREADS
> > using Apache/2.0.49 (worker MPM)
> >
> > waiting 300 seconds for server to start: ....[Wed Aug 18 15:31:46 2004] [error] Can't locate Apache/ServerRec.pm
>
> Jie, please show us the output of:
>
> cd modperl-2.0
> find . | grep 'Apache/ServerRec\.pm'
>
> it should be:
>
> ./blib/lib/Apache2/Apache/ServerRec.pm
>
> is that directory in your blib/lib/Apache2? that's of course if you've
> built with MP_INST_APACHE2=1
>
> it looks like it may picks up some previously installed perl?
>
> Were you to submit a proper bug report, we would have known more. Please
> remember to follow http://perl.apache.org/bugs/. Thanks.
>
>
>
> --
> __________________________________________________________________
> 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
> For additional commands, e-mail: dev-help@perl.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Jie Gao <J....@isu.usyd.edu.au>.
On Wed, 18 Aug 2004, Stas Bekman wrote:
> Date: Wed, 18 Aug 2004 17:59:23 -0700
> From: Stas Bekman <st...@stason.org>
> To: Jie Gao <J....@isu.usyd.edu.au>
> Cc: mod_perl Dev <de...@perl.apache.org>
> Subject: Re: time for 1.99_15?
>
> Jie Gao wrote:
> >
> >
> > On Wed, 18 Aug 2004, Stas Bekman wrote:
> >
> >
> >>>>>- It required Chatbot::Eliza for make test to be successful;
> >>>>
> >>>>why? what was the error? the test should have been skipped, no?
> >>>
> >>>
> >>>I don't think it was skipped.
> >>
> >>But how do we know what was the error, if you didn't copy and paste the
> >>error? :)
> >
> >
> > After running make test a couple of times, the error message went over
> > the top of the screen, and I couldn't cut-and-paste. :-)
>
> Could you remove Chatbot/Eliza.pm from the perl tree and try again? Do you
> get it when running 'make test' or even if you run it as single test?
> redirect the output to the file so you will be able to get your hands on
> the error message :)
Yes I did remove it before running make test. The test skipped it.
Regards,
Jie
> > Anyway, the latest result of running make test is all clear. :-)
>
> Great, thanks.
>
> --
> __________________________________________________________________
> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Jie Gao wrote:
>
>
> On Wed, 18 Aug 2004, Stas Bekman wrote:
>
>
>>>>>- It required Chatbot::Eliza for make test to be successful;
>>>>
>>>>why? what was the error? the test should have been skipped, no?
>>>
>>>
>>>I don't think it was skipped.
>>
>>But how do we know what was the error, if you didn't copy and paste the
>>error? :)
>
>
> After running make test a couple of times, the error message went over
> the top of the screen, and I couldn't cut-and-paste. :-)
Could you remove Chatbot/Eliza.pm from the perl tree and try again? Do you
get it when running 'make test' or even if you run it as single test?
redirect the output to the file so you will be able to get your hands on
the error message :)
> Anyway, the latest result of running make test is all clear. :-)
Great, thanks.
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Jie Gao <J....@isu.usyd.edu.au>.
On Wed, 18 Aug 2004, Stas Bekman wrote:
> >>>- It required Chatbot::Eliza for make test to be successful;
> >>
> >>why? what was the error? the test should have been skipped, no?
> >
> >
> > I don't think it was skipped.
>
> But how do we know what was the error, if you didn't copy and paste the
> error? :)
After running make test a couple of times, the error message went over
the top of the screen, and I couldn't cut-and-paste. :-)
Anyway, the latest result of running make test is all clear. :-)
Cheers,
Jie
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Jie Gao wrote:
>
>
> On Wed, 18 Aug 2004, Stas Bekman wrote:
>
>
>>Date: Wed, 18 Aug 2004 14:34:47 -0700
>>From: Stas Bekman <st...@stason.org>
>>To: Jie Gao <J....@isu.usyd.edu.au>
>>Cc: mod_perl Dev <de...@perl.apache.org>
>>Subject: Re: time for 1.99_15?
>>
>>Jie Gao wrote:
>>
>>>
>>>On Wed, 18 Aug 2004, Stas Bekman wrote:
>>>
>>>
>>>
>>>>Date: Wed, 18 Aug 2004 00:20:03 -0700
>>>>From: Stas Bekman <st...@stason.org>
>>>>To: Jie Gao <J....@isu.usyd.edu.au>
>>>>Cc: mod_perl Dev <de...@perl.apache.org>
>>>>Subject: Re: time for 1.99_15?
>>>>
>>>>Jie Gao wrote:
>>>>
>>>>
>>>>>-------------8<---------- Start Bug Report ------------8<----------
>>>>>1. Problem Description:
>>>>>
>>>>> [DESCRIBE THE PROBLEM HERE]
>>>>>
>>>>>2. Used Components and their Configuration:
>>>>>
>>>>>*** mod_perl version 1.9914
>>>>
>>>>ah, this seems to be like a wrong report. Are you sure you are inside the
>>>>up-to-date cvs build?
>>>
>>>
>>>OK, I removed that directory and started afresh. The new problems are:
>>>
>>>- It required Chatbot::Eliza for make test to be successful;
>>
>>why? what was the error? the test should have been skipped, no?
>
>
> I don't think it was skipped.
But how do we know what was the error, if you didn't copy and paste the
error? :)
>>>- The following error:
>>>
>>>t/protocol/eliza........................ok
>>>t/protocol/pseudo_http..................NOK 2# Failed test 2 in t/protocol/pseudo_http.t at line 60
>>>t/protocol/pseudo_http..................NOK 3# Failed test 3 in t/protocol/pseudo_http.t at line 60 fail #2
>>>t/protocol/pseudo_http..................NOK 4# Failed test 4 in t/protocol/pseudo_http.t at line 60 fail #3
>>>t/protocol/pseudo_http..................NOK 5# Failed test 5 in t/protocol/pseudo_http.t at line 54
>>>t/protocol/pseudo_http..................NOK 6# Failed test 6 in t/protocol/pseudo_http.t at line 60 fail #4
>>>t/protocol/pseudo_http..................NOK 7# Failed test 7 in t/protocol/pseudo_http.t at line 60 fail #5
>>>t/protocol/pseudo_http..................NOK 8# Failed test 8 in t/protocol/pseudo_http.t at line 54 fail #2
>>>t/protocol/pseudo_http..................NOK 10# Failed test 10 in t/protocol/pseudo_http.t at line 60 fail #6
>>>t/protocol/pseudo_http..................NOK 11# Failed test 11 in t/protocol/pseudo_http.t at line 60 fail #7
>>>t/protocol/pseudo_http..................NOK 12# Failed test 12 in t/protocol/pseudo_http.t at line 60 fail #8
>>>t/protocol/pseudo_http..................NOK 13# Failed test 13 in t/protocol/pseudo_http.t at line 54 fail #3
>>>t/protocol/pseudo_http..................FAILED tests 2-8, 10-13
>>
>>you aren't running the latest cvs. there was a temp breakage which was
>>fixed a few minutes later. please try again with the latest cvs.
>
>
> OK. I'll try again. It'll take a while on my slow Sun box.
you don't need to rebuild everything, in this case just:
cvs up t/protocol/TestProtocol/pseudo_http.pm
:)
>>>- server does not shut down (tested twice);
>>>- Seems cvs does not get rid of/update some old files.
>>
>>what do you mean? what files?
>
>
> I don't know what files, but I had to remove the whole directory and started afresh, as I said.
I suppose it's the issue of 'make clean' doesn't cleaning well.
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Jie Gao <J....@isu.usyd.edu.au>.
On Wed, 18 Aug 2004, Stas Bekman wrote:
> Date: Wed, 18 Aug 2004 14:34:47 -0700
> From: Stas Bekman <st...@stason.org>
> To: Jie Gao <J....@isu.usyd.edu.au>
> Cc: mod_perl Dev <de...@perl.apache.org>
> Subject: Re: time for 1.99_15?
>
> Jie Gao wrote:
> >
> >
> > On Wed, 18 Aug 2004, Stas Bekman wrote:
> >
> >
> >>Date: Wed, 18 Aug 2004 00:20:03 -0700
> >>From: Stas Bekman <st...@stason.org>
> >>To: Jie Gao <J....@isu.usyd.edu.au>
> >>Cc: mod_perl Dev <de...@perl.apache.org>
> >>Subject: Re: time for 1.99_15?
> >>
> >>Jie Gao wrote:
> >>
> >>>-------------8<---------- Start Bug Report ------------8<----------
> >>>1. Problem Description:
> >>>
> >>> [DESCRIBE THE PROBLEM HERE]
> >>>
> >>>2. Used Components and their Configuration:
> >>>
> >>>*** mod_perl version 1.9914
> >>
> >>ah, this seems to be like a wrong report. Are you sure you are inside the
> >>up-to-date cvs build?
> >
> >
> > OK, I removed that directory and started afresh. The new problems are:
> >
> > - It required Chatbot::Eliza for make test to be successful;
>
> why? what was the error? the test should have been skipped, no?
I don't think it was skipped.
> > - The following error:
> >
> > t/protocol/eliza........................ok
> > t/protocol/pseudo_http..................NOK 2# Failed test 2 in t/protocol/pseudo_http.t at line 60
> > t/protocol/pseudo_http..................NOK 3# Failed test 3 in t/protocol/pseudo_http.t at line 60 fail #2
> > t/protocol/pseudo_http..................NOK 4# Failed test 4 in t/protocol/pseudo_http.t at line 60 fail #3
> > t/protocol/pseudo_http..................NOK 5# Failed test 5 in t/protocol/pseudo_http.t at line 54
> > t/protocol/pseudo_http..................NOK 6# Failed test 6 in t/protocol/pseudo_http.t at line 60 fail #4
> > t/protocol/pseudo_http..................NOK 7# Failed test 7 in t/protocol/pseudo_http.t at line 60 fail #5
> > t/protocol/pseudo_http..................NOK 8# Failed test 8 in t/protocol/pseudo_http.t at line 54 fail #2
> > t/protocol/pseudo_http..................NOK 10# Failed test 10 in t/protocol/pseudo_http.t at line 60 fail #6
> > t/protocol/pseudo_http..................NOK 11# Failed test 11 in t/protocol/pseudo_http.t at line 60 fail #7
> > t/protocol/pseudo_http..................NOK 12# Failed test 12 in t/protocol/pseudo_http.t at line 60 fail #8
> > t/protocol/pseudo_http..................NOK 13# Failed test 13 in t/protocol/pseudo_http.t at line 54 fail #3
> > t/protocol/pseudo_http..................FAILED tests 2-8, 10-13
>
> you aren't running the latest cvs. there was a temp breakage which was
> fixed a few minutes later. please try again with the latest cvs.
OK. I'll try again. It'll take a while on my slow Sun box.
> > - server does not shut down (tested twice);
> > - Seems cvs does not get rid of/update some old files.
>
> what do you mean? what files?
I don't know what files, but I had to remove the whole directory and started afresh, as I said.
Regards,
Jie
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Jie Gao wrote:
>
>
> On Wed, 18 Aug 2004, Stas Bekman wrote:
>
>
>>Date: Wed, 18 Aug 2004 00:20:03 -0700
>>From: Stas Bekman <st...@stason.org>
>>To: Jie Gao <J....@isu.usyd.edu.au>
>>Cc: mod_perl Dev <de...@perl.apache.org>
>>Subject: Re: time for 1.99_15?
>>
>>Jie Gao wrote:
>>
>>>-------------8<---------- Start Bug Report ------------8<----------
>>>1. Problem Description:
>>>
>>> [DESCRIBE THE PROBLEM HERE]
>>>
>>>2. Used Components and their Configuration:
>>>
>>>*** mod_perl version 1.9914
>>
>>ah, this seems to be like a wrong report. Are you sure you are inside the
>>up-to-date cvs build?
>
>
> OK, I removed that directory and started afresh. The new problems are:
>
> - It required Chatbot::Eliza for make test to be successful;
why? what was the error? the test should have been skipped, no?
> - The following error:
>
> t/protocol/eliza........................ok
> t/protocol/pseudo_http..................NOK 2# Failed test 2 in t/protocol/pseudo_http.t at line 60
> t/protocol/pseudo_http..................NOK 3# Failed test 3 in t/protocol/pseudo_http.t at line 60 fail #2
> t/protocol/pseudo_http..................NOK 4# Failed test 4 in t/protocol/pseudo_http.t at line 60 fail #3
> t/protocol/pseudo_http..................NOK 5# Failed test 5 in t/protocol/pseudo_http.t at line 54
> t/protocol/pseudo_http..................NOK 6# Failed test 6 in t/protocol/pseudo_http.t at line 60 fail #4
> t/protocol/pseudo_http..................NOK 7# Failed test 7 in t/protocol/pseudo_http.t at line 60 fail #5
> t/protocol/pseudo_http..................NOK 8# Failed test 8 in t/protocol/pseudo_http.t at line 54 fail #2
> t/protocol/pseudo_http..................NOK 10# Failed test 10 in t/protocol/pseudo_http.t at line 60 fail #6
> t/protocol/pseudo_http..................NOK 11# Failed test 11 in t/protocol/pseudo_http.t at line 60 fail #7
> t/protocol/pseudo_http..................NOK 12# Failed test 12 in t/protocol/pseudo_http.t at line 60 fail #8
> t/protocol/pseudo_http..................NOK 13# Failed test 13 in t/protocol/pseudo_http.t at line 54 fail #3
> t/protocol/pseudo_http..................FAILED tests 2-8, 10-13
you aren't running the latest cvs. there was a temp breakage which was
fixed a few minutes later. please try again with the latest cvs.
> - server does not shut down (tested twice);
> - Seems cvs does not get rid of/update some old files.
what do you mean? what files?
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Jie Gao wrote:
> -------------8<---------- Start Bug Report ------------8<----------
> 1. Problem Description:
>
> [DESCRIBE THE PROBLEM HERE]
>
> 2. Used Components and their Configuration:
>
> *** mod_perl version 1.9914
ah, this seems to be like a wrong report. Are you sure you are inside the
up-to-date cvs build?
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Jie Gao <J....@isu.usyd.edu.au>.
-------------8<---------- Start Bug Report ------------8<----------
1. Problem Description:
[DESCRIBE THE PROBLEM HERE]
2. Used Components and their Configuration:
*** mod_perl version 1.9914
*** using lib/Apache/BuildConfig.pm
*** Makefile.PL options:
MP_APR_LIB => aprext
MP_APXS => /usr/local/apache_2.0.49/bin/apxs
MP_COMPAT_1X => 1
MP_DEBUG => 1
MP_GENERATE_XS => 1
MP_LIBNAME => mod_perl
MP_TRACE => 1
MP_USE_DSO => 1
*** /usr/local/apache_2.0.49/bin/httpd -V
Server version: Apache/2.0.49
Server built: Mar 29 2004 12:00:23
Server's Module Magic Number: 20020903:7
Architecture: 32-bit
Server compiled with....
-D APACHE_MPM_DIR="server/mpm/worker"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_PROC_PTHREAD_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D HTTPD_ROOT="/usr/local/apache_2.0.49"
-D SUEXEC_BIN="/usr/local/apache_2.0.49/bin/suexec"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="conf/mime.types"
-D SERVER_CONFIG_FILE="conf/httpd.conf"
*** /usr/local/perl-5.8.3_threaded/bin/perl -V
Summary of my perl5 (revision 5.0 version 8 subversion 3) configuration:
Platform:
osname=solaris, osvers=2.9, archname=sun4-solaris-thread-multi
uname='sunos banquo 5.9 generic_112233-11 sun4u sparc sunw,ultra-5_10 '
config_args='-Dcc=gcc -B/usr/ccs/bin/ -Doptimize=-O3 -Uinstallusrbinperl -Dprefix=/usr/local/perl-5.8.3_threaded -Dusethreads -Ui_db -Uusemymalloc -Dlocincpth=/usr/local/include /opt/local/include /include /usr/include /opt/sfw/include -Dloclibpth=/usr/local/lib /opt/local/lib /usr/lib /usr/ccs/lib /opt/sfw/lib'
hint=recommended, useposix=true, d_sigaction=define
usethreads=define use5005threads=undef useithreads=define usemultiplicity=define
useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler:
cc='gcc -B/usr/ccs/bin/', ccflags ='-D_REENTRANT -fno-strict-aliasing -I/usr/local/include -I/opt/sfw/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64',
optimize='-O3',
cppflags='-D_REENTRANT -fno-strict-aliasing -I/usr/local/include -I/opt/sfw/include'
ccversion='', gccversion='3.3.2', gccosandvers='solaris2.9'
intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=4321
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
alignbytes=8, prototype=define
Linker and Libraries:
ld='gcc -B/usr/ccs/bin/', ldflags =' -L/usr/local/lib -L/usr/lib -L/usr/ccs/lib -L/opt/sfw/lib '
libpth=/usr/local/lib /usr/lib /usr/ccs/lib /opt/sfw/lib
libs=-lsocket -lnsl -lgdbm -ldl -lm -lpthread -lc
perllibs=-lsocket -lnsl -ldl -lm -lpthread -lc
libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a
gnulibc_version=''
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' '
cccdlflags='-fPIC', lddlflags='-G -L/usr/local/lib -L/usr/lib -L/usr/ccs/lib -L/opt/sfw/lib'
Characteristics of this binary (from libperl):
Compile-time options: MULTIPLICITY USE_ITHREADS USE_LARGE_FILES PERL_IMPLICIT_CONTEXT
Built under solaris
Compiled at Jan 31 2004 12:49:48
%ENV:
PERL_LWP_USE_HTTP_10="1"
@INC:
/usr/local/perl-5.8.3_threaded/lib/5.8.3/sun4-solaris-thread-multi
/usr/local/perl-5.8.3_threaded/lib/5.8.3
/usr/local/perl-5.8.3_threaded/lib/site_perl/5.8.3/sun4-solaris-thread-multi
/usr/local/perl-5.8.3_threaded/lib/site_perl/5.8.3
/usr/local/perl-5.8.3_threaded/lib/site_perl
.
3. This is the core dump trace: (if you get a core dump):
[CORE TRACE COMES HERE]
This report was generated by -e on Wed Aug 18 07:10:04 2004 GMT.
-------------8<---------- End Bug Report --------------8<----------
Note: Complete the rest of the details and post this bug report to
dev <at> perl.apache.org. To subscribe to the list send an empty
email to dev-subscribe@perl.apache.org.
On Tue, 17 Aug 2004, Stas Bekman wrote:
> Date: Tue, 17 Aug 2004 23:56:48 -0700
> From: Stas Bekman <st...@stason.org>
> To: Jie Gao <J....@isu.usyd.edu.au>
> Cc: mod_perl Dev <de...@perl.apache.org>
> Subject: Re: time for 1.99_15?
>
> Jie Gao wrote:
> > Hi Stas,
> >
> > perl-5.8.3_threaded + Latest cvs + apache_2.0.49
> > ------------------------------------------------
> >
> > make test fails with the error:
> >
> > ....
> > [warning] testing whether 'nobody' is able to -rwx /u0/local/src/modperl-2.0/t
> > "/usr/local/perl-5.8.3_threaded/bin/perl" -Mlib=/u0/local/src/modperl-2.0/Apache-Test/lib -MApache::TestRun -e
> > 'eval { Apache::TestRun::run_root_fs_test(60001, 60001, q[/u0/local/src/modperl-2.0/t]) }';
> >
> >
> > [warning] result: OK
> > [warning] the client side drops 'root' permissions and becomes 'nobody'
> > /usr/local/apache_2.0.49/bin/httpd -d /u0/local/src/modperl-2.0/t -f /u0/local/src/modperl-2.0/t/conf/httpd.conf
> > -D APACHE2 -D PERL_USEITHREADS
> > using Apache/2.0.49 (worker MPM)
> >
> > waiting 300 seconds for server to start: ....[Wed Aug 18 15:31:46 2004] [error] Can't locate Apache/ServerRec.pm
>
> Jie, please show us the output of:
>
> cd modperl-2.0
> find . | grep 'Apache/ServerRec\.pm'
>
> it should be:
>
> ./blib/lib/Apache2/Apache/ServerRec.pm
Not found.
>
> is that directory in your blib/lib/Apache2? that's of course if you've
> built with MP_INST_APACHE2=1
>
> it looks like it may picks up some previously installed perl?
>
> Were you to submit a proper bug report, we would have known more. Please
> remember to follow http://perl.apache.org/bugs/. Thanks.
>
>
>
> --
> __________________________________________________________________
> 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
> For additional commands, e-mail: dev-help@perl.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Jie Gao wrote:
> Hi Stas,
>
> perl-5.8.3_threaded + Latest cvs + apache_2.0.49
> ------------------------------------------------
>
> make test fails with the error:
>
> ....
> [warning] testing whether 'nobody' is able to -rwx /u0/local/src/modperl-2.0/t
> "/usr/local/perl-5.8.3_threaded/bin/perl" -Mlib=/u0/local/src/modperl-2.0/Apache-Test/lib -MApache::TestRun -e
> 'eval { Apache::TestRun::run_root_fs_test(60001, 60001, q[/u0/local/src/modperl-2.0/t]) }';
>
>
> [warning] result: OK
> [warning] the client side drops 'root' permissions and becomes 'nobody'
> /usr/local/apache_2.0.49/bin/httpd -d /u0/local/src/modperl-2.0/t -f /u0/local/src/modperl-2.0/t/conf/httpd.conf
> -D APACHE2 -D PERL_USEITHREADS
> using Apache/2.0.49 (worker MPM)
>
> waiting 300 seconds for server to start: ....[Wed Aug 18 15:31:46 2004] [error] Can't locate Apache/ServerRec.pm
Jie, please show us the output of:
cd modperl-2.0
find . | grep 'Apache/ServerRec\.pm'
it should be:
./blib/lib/Apache2/Apache/ServerRec.pm
is that directory in your blib/lib/Apache2? that's of course if you've
built with MP_INST_APACHE2=1
it looks like it may picks up some previously installed perl?
Were you to submit a proper bug report, we would have known more. Please
remember to follow http://perl.apache.org/bugs/. Thanks.
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Jie Gao <J....@isu.usyd.edu.au>.
Hi Stas,
perl-5.8.3_threaded + Latest cvs + apache_2.0.49
------------------------------------------------
make test fails with the error:
....
[warning] testing whether 'nobody' is able to -rwx /u0/local/src/modperl-2.0/t
"/usr/local/perl-5.8.3_threaded/bin/perl" -Mlib=/u0/local/src/modperl-2.0/Apache-Test/lib -MApache::TestRun -e
'eval { Apache::TestRun::run_root_fs_test(60001, 60001, q[/u0/local/src/modperl-2.0/t]) }';
[warning] result: OK
[warning] the client side drops 'root' permissions and becomes 'nobody'
/usr/local/apache_2.0.49/bin/httpd -d /u0/local/src/modperl-2.0/t -f /u0/local/src/modperl-2.0/t/conf/httpd.conf
-D APACHE2 -D PERL_USEITHREADS
using Apache/2.0.49 (worker MPM)
waiting 300 seconds for server to start: ....[Wed Aug 18 15:31:46 2004] [error] Can't locate Apache/ServerRec.pm
in @INC (@INC contains: /u0/local/src/modperl-2.0/t/lib /u0/local/src/modperl-2.0/Apache-Test/lib
/u0/local/src/modperl-2.0/blib/lib /u0/local/src/modperl-2.0/blib/arch /u0/local/src/modperl-2.0/t/response
/u0/local/src/modperl-2.0/t/protocol /u0/local/src/modperl-2.0/t/preconnection /u0/local/src/modperl-2.0/t/hooks
/u0/local/src/modperl-2.0/t/filter /u0/local/src/modperl-2.0/t
/u0/local/src/modperl-2.0/t/htdocs/testdirective/perlmodule-vh
/u0/local/src/modperl-2.0/t/htdocs/testdirective/main
/usr/local/perl-5.8.3_threaded/lib/5.8.3/sun4-solaris-thread-multi /usr/local/perl-5.8.3_threaded/lib/5.8.3
/usr/local/perl-5.8.3_threaded/lib/site_perl/5.8.3/sun4-solaris-thread-multi
/usr/local/perl-5.8.3_threaded/lib/site_perl/5.8.3 /usr/local/perl-5.8.3_threaded/lib/site_perl
/u0/local/src/modperl-2.0/t/ /u0/local/src/modperl-2.0/t/lib/perl) at
/u0/local/src/modperl-2.0/t/conf/modperl_extra.pl line 10.\nBEGIN failed--compilation aborted at
/u0/local/src/modperl-2.0/t/conf/modperl_extra.pl line 10.\nCompilation failed in require at
/u0/local/src/modperl-2.0/t/conf/modperl_startup.pl line 17.\n\t...propagated at
/u0/local/src/modperl-2.0/t/conf/modperl_startup.pl line 18.\nBEGIN failed--compilation aborted at
/u0/local/src/modperl-2.0/t/conf/modperl_startup.pl line 20.\nCompilation failed in require at (eval 2) line 1.\n
[Wed Aug 18 15:31:46 2004] [error] Can't load Perl file: /u0/local/src/modperl-2.0/t/conf/modperl_startup.pl for
server localhost:8529, exiting...
.......................................................................................................................................................................................................................................................................................................
waiting 300 seconds for server to start: not ok
[ error] giving up after 301 secs. If you think that your system
is slow or overloaded try again with a longer timeout value.
by setting the environment variable APACHE_TEST_STARTUP_TIMEOUT
to a high value (e.g. 600) and repeat the last command.
[ error] server failed to start! (t/logs/error_log wasn't created, start the server in the debug mode)
+--------------------------------------------------------+
| Please file a bug report: http://perl.apache.org/bugs/ |
+--------------------------------------------------------+
gmake: *** [run_tests] Error 1
Regards,
Jie
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Randy Kobes wrote:
> On Thu, 19 Aug 2004, Steve Hay wrote:
>
>
>>Randy Kobes wrote:
>
> [ ... ]
>
>>>Did you (or Markus?) see any problem with the modperl/pnotes
>>>test? Before I left I was getting a failure on one of the
>>>tests that tested if an entry exists - mine didn't. This
>>>was with an ActivePerl 810 compatible Win32 perl.
>>>
>>
>>No, no problems:
>>
>>t\modperl\pnotes....1..9
>># Running under perl version 5.008005 for MSWin32
>># Current time local: Thu Aug 19 18:08:29 2004
>># Current time GMT: Thu Aug 19 17:08:29 2004
>># Using Test.pm version 1.25
>># Using Apache/Test.pm version 1.13
>>ok 1
>># testing : $r->pnotes(key,val)
>># expected: pnotes_bar
>># received: pnotes_bar
>>ok 2
>># testing : $r->pnotes(key)
>># expected: pnotes_bar
>># received: pnotes_bar
>>ok 3
>># testing : ref($r->pnotes)
>># expected: HASH
>># received: HASH
>>ok 4
>># testing : $r->pnotes()->{}
>># expected: pnotes_bar
>># received: pnotes_bar
>>ok 5
>># testing : unset entry contents
>># expected: undef
>># received: undef
>>ok 6
>>ok 7
>># testing : deleted entry contents
>># expected: undef
>># received: undef
>>ok 8
>>ok 9
>>ok
>>All tests successful.
>>
>>This is with my own builds of 2.0.50 / 5.8.5 (perl -V below) and CVS
>>this morning (9am BST).
>
>
> This sounds similar to what Geoff found, so it may be
> a thing that's a problem with earlier perls (pre-5.8.5?).
> If that's the case cross-platform, perhaps that one
> subtest (7) could be skipped for pre-5.8.5?
I can reproduce the problem with 5.8.0, so I'll take care of it. Thanks
for pointing that out Geoff and Randy.
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Thu, 19 Aug 2004, Steve Hay wrote:
> Randy Kobes wrote:
[ ... ]
> >Did you (or Markus?) see any problem with the modperl/pnotes
> >test? Before I left I was getting a failure on one of the
> >tests that tested if an entry exists - mine didn't. This
> >was with an ActivePerl 810 compatible Win32 perl.
> >
> No, no problems:
>
> t\modperl\pnotes....1..9
> # Running under perl version 5.008005 for MSWin32
> # Current time local: Thu Aug 19 18:08:29 2004
> # Current time GMT: Thu Aug 19 17:08:29 2004
> # Using Test.pm version 1.25
> # Using Apache/Test.pm version 1.13
> ok 1
> # testing : $r->pnotes(key,val)
> # expected: pnotes_bar
> # received: pnotes_bar
> ok 2
> # testing : $r->pnotes(key)
> # expected: pnotes_bar
> # received: pnotes_bar
> ok 3
> # testing : ref($r->pnotes)
> # expected: HASH
> # received: HASH
> ok 4
> # testing : $r->pnotes()->{}
> # expected: pnotes_bar
> # received: pnotes_bar
> ok 5
> # testing : unset entry contents
> # expected: undef
> # received: undef
> ok 6
> ok 7
> # testing : deleted entry contents
> # expected: undef
> # received: undef
> ok 8
> ok 9
> ok
> All tests successful.
>
> This is with my own builds of 2.0.50 / 5.8.5 (perl -V below) and CVS
> this morning (9am BST).
This sounds similar to what Geoff found, so it may be
a thing that's a problem with earlier perls (pre-5.8.5?).
If that's the case cross-platform, perhaps that one
subtest (7) could be skipped for pre-5.8.5?
--
best regards,
randy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Steve Hay <st...@uk.radan.com>.
Randy Kobes wrote:
>On Thu, 19 Aug 2004, Steve Hay wrote:
>
>
>
>>Looks like they're all fixed now: current CVS passes all tests (incl
>>ModPerl-Registry)!
>>
>>
>
>Did you (or Markus?) see any problem with the modperl/pnotes
>test? Before I left I was getting a failure on one of the
>tests that tested if an entry exists - mine didn't. This
>was with an ActivePerl 810 compatible Win32 perl.
>
No, no problems:
t\modperl\pnotes....1..9
# Running under perl version 5.008005 for MSWin32
# Current time local: Thu Aug 19 18:08:29 2004
# Current time GMT: Thu Aug 19 17:08:29 2004
# Using Test.pm version 1.25
# Using Apache/Test.pm version 1.13
ok 1
# testing : $r->pnotes(key,val)
# expected: pnotes_bar
# received: pnotes_bar
ok 2
# testing : $r->pnotes(key)
# expected: pnotes_bar
# received: pnotes_bar
ok 3
# testing : ref($r->pnotes)
# expected: HASH
# received: HASH
ok 4
# testing : $r->pnotes()->{}
# expected: pnotes_bar
# received: pnotes_bar
ok 5
# testing : unset entry contents
# expected: undef
# received: undef
ok 6
ok 7
# testing : deleted entry contents
# expected: undef
# received: undef
ok 8
ok 9
ok
All tests successful.
This is with my own builds of 2.0.50 / 5.8.5 (perl -V below) and CVS
this morning (9am BST).
- Steve
Summary of my perl5 (revision 5 version 8 subversion 5) configuration:
Platform:
osname=MSWin32, osvers=4.0, archname=MSWin32-x86-multi-thread
uname=''
config_args='undef'
hint=recommended, useposix=true, d_sigaction=undef
usethreads=undef use5005threads=undef useithreads=define
usemultiplicity=define
useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler:
cc='cl', ccflags ='-nologo -Gf -W3 -Od -MD -Zi -DDEBUGGING -DWIN32
-D_CONSOLE -DNO_STRICT -DHAVE_DES_FCRYPT -DPERL_IMPLICIT_CONTEXT
-DPERL_IMPLICIT_SYS -DUSE_PERLIO -DPERL_MSVCRT_READFIX',
optimize='-Od -MD -Zi -DDEBUGGING',
cppflags='-DWIN32'
ccversion='', gccversion='', gccosandvers=''
intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
d_longlong=undef, longlongsize=8, d_longdbl=define, longdblsize=10
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='__int64',
lseeksize=8
alignbytes=8, prototype=define
Linker and Libraries:
ld='link', ldflags ='-nologo -nodefaultlib -debug
-libpath:"C:\apache2\perl5\lib\CORE" -machine:x86'
libpth=C:\PROGRA~1\MICROS~2\VC98\lib
libs= oldnames.lib kernel32.lib user32.lib gdi32.lib winspool.lib
comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib
netapi32.lib uuid.lib wsock32.lib mpr.lib winmm.lib version.lib
odbc32.lib odbccp32.lib msvcrt.lib
perllibs= oldnames.lib kernel32.lib user32.lib gdi32.lib
winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib
oleaut32.lib netapi32.lib uuid.lib wsock32.lib mpr.lib winmm.lib
version.lib odbc32.lib odbccp32.lib msvcrt.lib
libc=msvcrt.lib, so=dll, useshrplib=yes, libperl=perl58.lib
gnulibc_version='undef'
Dynamic Linking:
dlsrc=dl_win32.xs, dlext=dll, d_dlsymun=undef, ccdlflags=' '
cccdlflags=' ', lddlflags='-dll -nologo -nodefaultlib -debug
-libpath:"C:\apache2\perl5\lib\CORE" -machine:x86'
Characteristics of this binary (from libperl):
Compile-time options: DEBUGGING MULTIPLICITY USE_ITHREADS
USE_LARGE_FILES PERL_IMPLICIT_CONTEXT PERL_IMPLICIT_SYS
Locally applied patches:
23128 Use VirtualAlloc() more flexibly to mimic UNIX's sbrk()
Built under MSWin32
Compiled at Aug 18 2004 10:53:55
@INC:
C:/apache2/perl5/lib
C:/apache2/perl5/site/lib
.
------------------------------------------------
Radan Computational Ltd.
The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Thu, 19 Aug 2004, Steve Hay wrote:
> Looks like they're all fixed now: current CVS passes all tests (incl
> ModPerl-Registry)!
Did you (or Markus?) see any problem with the modperl/pnotes
test? Before I left I was getting a failure on one of the
tests that tested if an entry exists - mine didn't. This
was with an ActivePerl 810 compatible Win32 perl.
>
> Thanks to Markus too -- it's nice to have another Win32 developer around :)
Very true - thanks, Markus!
--
best regards,
randy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Steve Hay <st...@uk.radan.com>.
Randy Kobes wrote:
>On Tue, 17 Aug 2004, Stas Bekman wrote:
>
>
>
>>So, do we have any showstoppers for 1.99_15 release? Should some tests be
>>excluded from the distro?
>>
>>
>
>Apart from the problem you found today with the segfault,
>I'd say (but perhaps Steve has a better feeling) that,
>as far as Win32 goes, the current problems with the tests
>are fairly isolated, so shouldn't hold up a release on
>that account. I'll be back in a few days to look at them,
>though it seems Steve has a good handle so far.
>
Looks like they're all fixed now: current CVS passes all tests (incl
ModPerl-Registry)!
Thanks to Markus too -- it's nice to have another Win32 developer around :)
Time to dust off your RM cap, Stas!
- Steve
------------------------------------------------
Radan Computational Ltd.
The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Randy Kobes wrote:
> On Tue, 17 Aug 2004, Stas Bekman wrote:
>
>
>>So, do we have any showstoppers for 1.99_15 release? Should some tests be
>>excluded from the distro?
>
>
> Apart from the problem you found today with the segfault,
> I'd say (but perhaps Steve has a better feeling) that,
> as far as Win32 goes, the current problems with the tests
> are fairly isolated, so shouldn't hold up a release on
> that account. I'll be back in a few days to look at them,
> though it seems Steve has a good handle so far.
Excellent.
I'm going to look for my RM cap, not sure if I washed it
I'll poke around a bit first then to see if I can fix those quickly (and
not add new breakages).
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Tue, 17 Aug 2004, Stas Bekman wrote:
> So, do we have any showstoppers for 1.99_15 release? Should some tests be
> excluded from the distro?
Apart from the problem you found today with the segfault,
I'd say (but perhaps Steve has a better feeling) that,
as far as Win32 goes, the current problems with the tests
are fairly isolated, so shouldn't hold up a release on
that account. I'll be back in a few days to look at them,
though it seems Steve has a good handle so far.
--
best regards,
randy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
So, do we have any showstoppers for 1.99_15 release? Should some tests be
excluded from the distro?
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Fri, 13 Aug 2004, Steve Hay wrote:
> Geoffrey Young wrote:
>
> >Stas Bekman wrote:
> >
> >
> >>Yesterday I've fixed the problems that were showstoppers for the _15
> >>release. Any objections for doing it in the next few days?
> >>
> >>If there are none, any volunteers to do this release?
> >>
> >>We could get an RC right now, let it cook over the weekend and if
> >>everything goes well release on Monday?
> >>
> >>
> >
> >in general I don't think much testing gets done over the weekend, so if
> >you're serious about getting candidate results better to let it sit until
> >tuesday so that people can test on monday (as the EU people have gone to the
> >pub already today).
> >
> I would agree with that (being in the UK and knowing that I won't be
> doing this stuff over the weekend (starting about now!) ;)
>
> Just tried the latest CVS with 2.0.49 / 5.8.4 (I really must upgrade
> them sometime too!):
>
> Failed Test Stat Wstat Total Fail Failed List of Failed
> -------------------------------------------------------------------------------
> t\filter\out_bbs_filebucket.t 10 10 100.00% 1-10
> t\hooks\authen_digest.t 7 1 14.29% 7
> 7 tests and 12 subtests skipped.
> Failed 2/210 test scripts, 99.05% okay. 11/3691 subtests failed, 99.70%
> okay.
>
> (I also got "Scalars leaked: 1" twice from t\perl\ithreads.t)
>
> More details separately.
Unfortunately, I'm away for the next week, and can't test
this out. It'd be great if you had the time, Steve; I
didn't make up a ppm package based on the current mp2
CPAN version due to some problems (that were subsequently
solved in the -dev ppm package), so it'd be nice if at
least most of the tests could pass on Win32, or at least
have understandable failures, so that a ppm package
could be made. Thanks.
--
best regards,
randy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Stas Bekman wrote:
> Steve Hay wrote:
>
>> Stas Bekman wrote:
>>
>>
>>> Steve Hay wrote:
>>>
>>>
>>>
>>>> ModPerl-Registry test all OK, but with these warnings twice over (once
>>>
>>>
>>>> from t\closure.t and once from t\perlrun_extload.t):
>>>
>>>
>>>> Prototype mismatch: sub
>>>> ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_cmp:
>>>> none vs ($$;$) at C:/apache2/perl5/lib/Exporter.pm line 65.
>>>> at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
>>>> Prototype mismatch: sub
>>>> ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_is_equal:
>>>> none vs ($$) at C:/apache2/perl5/lib/Exporter.pm line 65.
>>>> at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
>>>> Prototype mismatch: sub
>>>> ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_filepath_cmp:
>>>> none vs ($$;$) at C:/apache2/perl5/lib/Exporter.pm line 65.
>>>> at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
>>>>
>>>
>>>
>>> Yup, it's because of the reload of the CODE which was deleted. I'm
>>> not sure what can be done about these. Some time ago, I've spent a
>>> lot of time trying to get rid of those, working with p5p, but it
>>> didn't work out. The delete CODE refs (which we do in
>>> ModPerl::PerlRun) is as good as it gets.
>>>
>>
>> I remember we looked at improving Apache::Reload a while ago to help
>> it clean up redefined subs better. Is that the kind of thing you
>> need? Philippe posted a brilliant piece of code at the time to do that.
>>
>> Even better would be to go back to the Apache::Reload questions and
>> sort that out too...
>
>
> Absolutely, that thread has somehow died out. Philippe can you go back
> review where we have left that thread [1] and get those things finally
> fixed? Thanks.
Yes, no problem. I need to polish off on the few PODs I am supposed to
finish, then I would have needed to pick an issue
out of todo/release, so I'll tackle the Apache::Reload issue next.
> [1]
> http://marc.theaimsgroup.com/?t=105545915700001&r=1&w=2
> http://marc.theaimsgroup.com/?t=108619620600001&r=1&w=2
>
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Steve Hay wrote:
> Stas Bekman wrote:
>
>
>>Steve Hay wrote:
>>
>>
>>
>>>ModPerl-Registry test all OK, but with these warnings twice over (once
>>
>>>from t\closure.t and once from t\perlrun_extload.t):
>>
>>>Prototype mismatch: sub
>>>ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_cmp:
>>>none vs ($$;$) at C:/apache2/perl5/lib/Exporter.pm line 65.
>>>at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
>>>Prototype mismatch: sub
>>>ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_is_equal:
>>>none vs ($$) at C:/apache2/perl5/lib/Exporter.pm line 65.
>>>at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
>>>Prototype mismatch: sub
>>>ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_filepath_cmp:
>>>none vs ($$;$) at C:/apache2/perl5/lib/Exporter.pm line 65.
>>>at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
>>>
>>>
>>
>>Yup, it's because of the reload of the CODE which was deleted. I'm not
>>sure what can be done about these. Some time ago, I've spent a lot of
>>time trying to get rid of those, working with p5p, but it didn't work
>>out. The delete CODE refs (which we do in ModPerl::PerlRun) is as good
>>as it gets.
>>
>
> I remember we looked at improving Apache::Reload a while ago to help it
> clean up redefined subs better. Is that the kind of thing you need?
> Philippe posted a brilliant piece of code at the time to do that.
>
> Even better would be to go back to the Apache::Reload questions and sort
> that out too...
Absolutely, that thread has somehow died out. Philippe can you go back
review where we have left that thread [1] and get those things finally
fixed? Thanks.
[1]
http://marc.theaimsgroup.com/?t=105545915700001&r=1&w=2
http://marc.theaimsgroup.com/?t=108619620600001&r=1&w=2
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Steve Hay <st...@uk.radan.com>.
Stas Bekman wrote:
>Steve Hay wrote:
>
>
>>ModPerl-Registry test all OK, but with these warnings twice over (once
>>from t\closure.t and once from t\perlrun_extload.t):
>>
>>Prototype mismatch: sub
>>ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_cmp:
>>none vs ($$;$) at C:/apache2/perl5/lib/Exporter.pm line 65.
>> at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
>>Prototype mismatch: sub
>>ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_is_equal:
>>none vs ($$) at C:/apache2/perl5/lib/Exporter.pm line 65.
>> at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
>>Prototype mismatch: sub
>>ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_filepath_cmp:
>>none vs ($$;$) at C:/apache2/perl5/lib/Exporter.pm line 65.
>> at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
>>
>>
>
>Yup, it's because of the reload of the CODE which was deleted. I'm not
>sure what can be done about these. Some time ago, I've spent a lot of
>time trying to get rid of those, working with p5p, but it didn't work
>out. The delete CODE refs (which we do in ModPerl::PerlRun) is as good
>as it gets.
>
I remember we looked at improving Apache::Reload a while ago to help it
clean up redefined subs better. Is that the kind of thing you need?
Philippe posted a brilliant piece of code at the time to do that.
Even better would be to go back to the Apache::Reload questions and sort
that out too...
- Steve
------------------------------------------------
Radan Computational Ltd.
The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Randy Kobes wrote:
> On Sun, 15 Aug 2004, Stas Bekman wrote:
> [ .. ]
>
>>No. Normally those happen after the handler has been run
>>already. How come do you get them on the client side? Is
>>the client leaking those? (doesn't make sense). Or is it
>>something specific to win32, where server logs end up on
>>the client side? Do you have those leak logs in error_log
>>too?
>
>
> Sometimes on Win32 it happens that the messages
> intended for the server error log end up on the
> client side. The last time I tried those messages
> about a leak didn't appear in the error log.
Hmm, so there is nothing programmatical that t/SMOKE could get hold of.
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Sun, 15 Aug 2004, Stas Bekman wrote:
[ .. ]
> No. Normally those happen after the handler has been run
> already. How come do you get them on the client side? Is
> the client leaking those? (doesn't make sense). Or is it
> something specific to win32, where server logs end up on
> the client side? Do you have those leak logs in error_log
> too?
Sometimes on Win32 it happens that the messages
intended for the server error log end up on the
client side. The last time I tried those messages
about a leak didn't appear in the error log.
--
best regards,
randy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Markus Wichitill wrote:
> Stas Bekman wrote:
>
>>> It seemed completely consistent to me. "nmake test" with mod_include
>>> always leaks, "nmake test" without mod_include and partial tests
>>> don't leak. Of course the long runtime of full tests has limited the
>>> number of tests I could run.
>>
>>
>> But does the test fail or not? If it doesn't then t/SMOKE won't help
>> here.
>
>
> No, it didn't ever actually fail.
>
> t\perl\ithreads.........................Scalars leaked: 1
> Scalars leaked: 1
> t\perl\ithreads.........................ok
>
> And since the FATAL switch is already used, I guess those warnings can't
> be easily turned into failures?
No. Normally those happen after the handler has been run already. How come
do you get them on the client side? Is the client leaking those? (doesn't
make sense). Or is it something specific to win32, where server logs end
up on the client side? Do you have those leak logs in error_log too?
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Markus Wichitill <ma...@gmx.de>.
Stas Bekman wrote:
>> Markus Wichitill wrote:
>>> t\perl\ithreads.........................Attempt to free temp
>>> prematurely: SV 0x6cc4a14, Perl interpreter: 0x6c90cfc at
>>> C:\Dev\debug\modperl-2.0\t\response/TestPerl/ithreads.pm line 44.
>>> request has failed (the response code was: 500)
>>>
>>> Seems to have crashed Apache, as all later tests failed (but I forgot
>>> to look at the process list to check if it was really gone). No crash
>>> popup this time, so no JIT debugging. Didn't see anything in the
>>> error_log. Can't reproduce it anymore.
>>
>> I now always get this. Apache exits, but doesn't crash in a way that
>> would allow me to debug it. If I attach the debugger during the "nmake
>> test" execution, all I see is:
>>
>> [...]
>> Loaded symbols for 'C:\Dev\debug\perl\lib\auto\Encode\Encode.dll'
>> The thread 0x3BC has exited with code 9 (0x9).
>> The thread 0xEC has exited with code 9 (0x9).
>> The thread 0x5FC has exited with code 9 (0x9).
>> [more threads]
>> The program 'C:\Dev\debug\apache\bin\apache.exe' has exited with code
>> 9 (0x9).
>
> If you can reliably get this problem, we need to figure what tests
> sequence causes it, before we can even start solving it. You could try
> to do that manually (with a binary search). Or if you can get hold of
> some error messages in the error_log you could adjust TestSmoke.pm to
> check those after runnin each test. It already checks for a core file
> after each test is run and considers the test to be failure if it finds
> one. So you could add another hook, and check error_log (for which it
> already holds the pointer in the filehandle, which is moved after each
> test) for custom error messages.
Manual search would be cruel, there's nothing in the log, and there's no
coredumps on Win32 - but since this, unlike the leak issue, is a real
failure, I've run
perl t\SMOKE -order=rotate -times=1 -verbose
which yields the reduced sequence
perl t\TEST -verbose t\filter\in_bbs_msg.t t\filter\in_bbs_underrun.t
t\filter\in_error.t t\filter\in_init_basic.t t\perl\ithreads.t
ithreads.t in that sequence doesn't fail with the same "Attempt to free temp
prematurely" error however, but with the "OS 10053" error from my
"t\apache\discard_rbody.t smoked" thread that went nowhere. Oh well.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Markus Wichitill wrote:
> Markus Wichitill wrote:
>
>>> t\perl\ithreads.........................Scalars leaked: 1
>>> Scalars leaked: 1
>>> t\perl\ithreads.........................ok
>>
>>
>> Just now I got this instead:
>>
>> t\perl\ithreads.........................Attempt to free temp
>> prematurely: SV 0x6cc4a14, Perl interpreter: 0x6c90cfc at
>> C:\Dev\debug\modperl-2.0\t\response/TestPerl/ithreads.pm line 44.
>> request has failed (the response code was: 500)
>>
>> Seems to have crashed Apache, as all later tests failed (but I forgot
>> to look at the process list to check if it was really gone). No crash
>> popup this time, so no JIT debugging. Didn't see anything in the
>> error_log. Can't reproduce it anymore.
>
>
> I now always get this. Apache exits, but doesn't crash in a way that
> would allow me to debug it. If I attach the debugger during the "nmake
> test" execution, all I see is:
>
> [...]
> Loaded symbols for 'C:\Dev\debug\perl\lib\auto\Encode\Encode.dll'
> The thread 0x3BC has exited with code 9 (0x9).
> The thread 0xEC has exited with code 9 (0x9).
> The thread 0x5FC has exited with code 9 (0x9).
> [more threads]
> The program 'C:\Dev\debug\apache\bin\apache.exe' has exited with code 9
> (0x9).
>
> At first I had suspected the new module reload voodoo, but removing that
> test didn't help.
If you can reliably get this problem, we need to figure what tests
sequence causes it, before we can even start solving it. You could try to
do that manually (with a binary search). Or if you can get hold of some
error messages in the error_log you could adjust TestSmoke.pm to check
those after runnin each test. It already checks for a core file after each
test is run and considers the test to be failure if it finds one. So you
could add another hook, and check error_log (for which it already holds
the pointer in the filehandle, which is moved after each test) for custom
error messages.
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Markus Wichitill <ma...@gmx.de>.
Markus Wichitill wrote:
>> t\perl\ithreads.........................Scalars leaked: 1
>> Scalars leaked: 1
>> t\perl\ithreads.........................ok
>
> Just now I got this instead:
>
> t\perl\ithreads.........................Attempt to free temp
> prematurely: SV 0x6cc4a14, Perl interpreter: 0x6c90cfc at
> C:\Dev\debug\modperl-2.0\t\response/TestPerl/ithreads.pm line 44.
> request has failed (the response code was: 500)
>
> Seems to have crashed Apache, as all later tests failed (but I forgot to
> look at the process list to check if it was really gone). No crash popup
> this time, so no JIT debugging. Didn't see anything in the error_log.
> Can't reproduce it anymore.
I now always get this. Apache exits, but doesn't crash in a way that would
allow me to debug it. If I attach the debugger during the "nmake test"
execution, all I see is:
[...]
Loaded symbols for 'C:\Dev\debug\perl\lib\auto\Encode\Encode.dll'
The thread 0x3BC has exited with code 9 (0x9).
The thread 0xEC has exited with code 9 (0x9).
The thread 0x5FC has exited with code 9 (0x9).
[more threads]
The program 'C:\Dev\debug\apache\bin\apache.exe' has exited with code 9 (0x9).
At first I had suspected the new module reload voodoo, but removing that
test didn't help.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Markus Wichitill wrote:
> Markus Wichitill wrote:
>
>> t\perl\ithreads.........................Scalars leaked: 1
>> Scalars leaked: 1
>> t\perl\ithreads.........................ok
>
>
> Just now I got this instead:
>
> t\perl\ithreads.........................Attempt to free temp
> prematurely: SV 0x6cc4a14, Perl interpreter: 0x6c90cfc at
> C:\Dev\debug\modperl-2.0\t\response/TestPerl/ithreads.pm line 44.
> request has failed (the response code was: 500)
>
> Seems to have crashed Apache, as all later tests failed (but I forgot to
> look at the process list to check if it was really gone). No crash popup
> this time, so no JIT debugging. Didn't see anything in the error_log.
> Can't reproduce it anymore.
Yup, I get it occassionaly too (absolutely randomly), I'd blame ithreads
for that. may be we should exclude it from the release test suite.
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Markus Wichitill <ma...@gmx.de>.
Markus Wichitill wrote:
> t\perl\ithreads.........................Scalars leaked: 1
> Scalars leaked: 1
> t\perl\ithreads.........................ok
Just now I got this instead:
t\perl\ithreads.........................Attempt to free temp prematurely: SV
0x6cc4a14, Perl interpreter: 0x6c90cfc at
C:\Dev\debug\modperl-2.0\t\response/TestPerl/ithreads.pm line 44.
request has failed (the response code was: 500)
Seems to have crashed Apache, as all later tests failed (but I forgot to
look at the process list to check if it was really gone). No crash popup
this time, so no JIT debugging. Didn't see anything in the error_log. Can't
reproduce it anymore.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Markus Wichitill <ma...@gmx.de>.
Stas Bekman wrote:
>> It seemed completely consistent to me. "nmake test" with mod_include
>> always leaks, "nmake test" without mod_include and partial tests don't
>> leak. Of course the long runtime of full tests has limited the number
>> of tests I could run.
>
> But does the test fail or not? If it doesn't then t/SMOKE won't help here.
No, it didn't ever actually fail.
t\perl\ithreads.........................Scalars leaked: 1
Scalars leaked: 1
t\perl\ithreads.........................ok
And since the FATAL switch is already used, I guess those warnings can't be
easily turned into failures?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Markus Wichitill wrote:
> Stas Bekman wrote:
>
>> Markus Wichitill wrote:
>>
>>> I know that the tests are skipped if mod_include isn't enabled in the
>>> system httpd.conf, that's why I enabled it (as well as mod_auth* and
>>> mod_proxy*), but I can't say for sure if it's the tests or the mere
>>> presence of mod_include that's triggering the leaks. The code in
>>> ithreads.pm certainly doesn't look like it should be influenced by
>>> either (?).
>>>
>>> If I run ithreads.t on its own, it doesn't leak, the same is true for
>>> every combination of one of the six tests and ithreads.t (perl t\TEST
>>> t/modules/include.t t/perl/ithreads.t). Which isn't particularly
>>> helpful...
>>
>>
>> Same here. I can't figure out the sequence that leads to this problem
>> as it always happens randomly. Though if you have a strong machine
>> t/SMOKE should help. That's of course if the test fails (which is the
>> case for me, but it is not consistent) It that the case for you?
>
>
> It seemed completely consistent to me. "nmake test" with mod_include
> always leaks, "nmake test" without mod_include and partial tests don't
> leak. Of course the long runtime of full tests has limited the number of
> tests I could run.
But does the test fail or not? If it doesn't then t/SMOKE won't help here.
> Any specific parameters I should pass to SMOKE? I've never used any
> smoke test so far. Mind you, I can only run that stuff during nights,
> and only while the stupid graphics card fan doesn't act up...
It's all documented here:
http://search.cpan.org/dist/Apache-Test/lib/Apache/TestSmoke.pm
Unless you already know a subgroup of failing test, then you just run it
as t/TEST. But you probably want to run it as:
t/SMOKE -order=rotate -times=1
since it's the normal (sorted) sequence that causes the problem. But
again, it'll only work if the test fails or dumps core.
It should be possible to modify the smoking to detect other problem (like
scanning error_log for certain errors), but at the moment it's not
supported (shouldn't be too hard to add).
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Markus Wichitill <ma...@gmx.de>.
Stas Bekman wrote:
> Markus Wichitill wrote:
>> I know that the tests are skipped if mod_include isn't enabled in the
>> system httpd.conf, that's why I enabled it (as well as mod_auth* and
>> mod_proxy*), but I can't say for sure if it's the tests or the mere
>> presence of mod_include that's triggering the leaks. The code in
>> ithreads.pm certainly doesn't look like it should be influenced by
>> either (?).
>>
>> If I run ithreads.t on its own, it doesn't leak, the same is true for
>> every combination of one of the six tests and ithreads.t (perl t\TEST
>> t/modules/include.t t/perl/ithreads.t). Which isn't particularly
>> helpful...
>
> Same here. I can't figure out the sequence that leads to this problem as
> it always happens randomly. Though if you have a strong machine t/SMOKE
> should help. That's of course if the test fails (which is the case for
> me, but it is not consistent) It that the case for you?
It seemed completely consistent to me. "nmake test" with mod_include always
leaks, "nmake test" without mod_include and partial tests don't leak. Of
course the long runtime of full tests has limited the number of tests I
could run.
Any specific parameters I should pass to SMOKE? I've never used any smoke
test so far. Mind you, I can only run that stuff during nights, and only
while the stupid graphics card fan doesn't act up...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Markus Wichitill wrote:
> Stas Bekman wrote:
>
>>> FWIW, I only seem to get the leaked scalar when I have mod_include
>>> enabled. I've done some test runs to make sure that it's not simply
>>> the number of loaded modules.
>>
>>
>> mod_include enabled, or tests that involve mod_include running? which
>> is the same thing, since if it's not enabled they are skipped :)
>
>
> I know that the tests are skipped if mod_include isn't enabled in the
> system httpd.conf, that's why I enabled it (as well as mod_auth* and
> mod_proxy*), but I can't say for sure if it's the tests or the mere
> presence of mod_include that's triggering the leaks. The code in
> ithreads.pm certainly doesn't look like it should be influenced by
> either (?).
>
> If I run ithreads.t on its own, it doesn't leak, the same is true for
> every combination of one of the six tests and ithreads.t (perl t\TEST
> t/modules/include.t t/perl/ithreads.t). Which isn't particularly helpful...
Same here. I can't figure out the sequence that leads to this problem as
it always happens randomly. Though if you have a strong machine t/SMOKE
should help. That's of course if the test fails (which is the case for me,
but it is not consistent) It that the case for you?
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Markus Wichitill <ma...@gmx.de>.
Stas Bekman wrote:
>> FWIW, I only seem to get the leaked scalar when I have mod_include
>> enabled. I've done some test runs to make sure that it's not simply
>> the number of loaded modules.
>
> mod_include enabled, or tests that involve mod_include running? which is
> the same thing, since if it's not enabled they are skipped :)
I know that the tests are skipped if mod_include isn't enabled in the system
httpd.conf, that's why I enabled it (as well as mod_auth* and mod_proxy*),
but I can't say for sure if it's the tests or the mere presence of
mod_include that's triggering the leaks. The code in ithreads.pm certainly
doesn't look like it should be influenced by either (?).
If I run ithreads.t on its own, it doesn't leak, the same is true for every
combination of one of the six tests and ithreads.t (perl t\TEST
t/modules/include.t t/perl/ithreads.t). Which isn't particularly helpful...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Markus Wichitill wrote:
> Stas Bekman wrote:
>
>>> (I also got "Scalars leaked: 1" twice from t\perl\ithreads.t)
>>
>>
>> I get those too once in a while, and sometimes failures, nothing has
>> changed here.
>
>
> FWIW, I only seem to get the leaked scalar when I have mod_include
> enabled. I've done some test runs to make sure that it's not simply the
> number of loaded modules.
mod_include enabled, or tests that involve mod_include running? which is
the same thing, since if it's not enabled they are skipped :) so if you
don't run tests that require mod_include, everything is fine? The tests
that require mod_include at the moment are:
t/filter/both_str_req_mix.t
t/filter/out_str_req_eos.t
t/filter/out_str_req_mix.t
t/modules/include.t
t/modules/include_subreq.t
t/modules/include2.t
I get occasional failures of t/perl/ithreads.t with the same error.
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Markus Wichitill <ma...@gmx.de>.
Stas Bekman wrote:
>> (I also got "Scalars leaked: 1" twice from t\perl\ithreads.t)
>
> I get those too once in a while, and sometimes failures, nothing has
> changed here.
FWIW, I only seem to get the leaked scalar when I have mod_include enabled.
I've done some test runs to make sure that it's not simply the number of
loaded modules.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Stas Bekman <st...@stason.org>.
Steve Hay wrote:
> Geoffrey Young wrote:
>
>
>>Stas Bekman wrote:
>>
>>
>>
>>>Yesterday I've fixed the problems that were showstoppers for the _15
>>>release. Any objections for doing it in the next few days?
>>>
>>>If there are none, any volunteers to do this release?
>>>
>>>We could get an RC right now, let it cook over the weekend and if
>>>everything goes well release on Monday?
>>>
>>>
>>
>>in general I don't think much testing gets done over the weekend, so if
>>you're serious about getting candidate results better to let it sit until
>>tuesday so that people can test on monday (as the EU people have gone to the
>>pub already today).
>>
>
> I would agree with that (being in the UK and knowing that I won't be
> doing this stuff over the weekend (starting about now!) ;)
:)
> Just tried the latest CVS with 2.0.49 / 5.8.4 (I really must upgrade
> them sometime too!):
>
> Failed Test Stat Wstat Total Fail Failed List of Failed
> -------------------------------------------------------------------------------
> t\filter\out_bbs_filebucket.t 10 10 100.00% 1-10
> t\hooks\authen_digest.t 7 1 14.29% 7
> 7 tests and 12 subtests skipped.
> Failed 2/210 test scripts, 99.05% okay. 11/3691 subtests failed, 99.70%
> okay.
Thanks Steve
> (I also got "Scalars leaked: 1" twice from t\perl\ithreads.t)
I get those too once in a while, and sometimes failures, nothing has
changed here.
> More details separately.
>
> ModPerl-Registry test all OK, but with these warnings twice over (once
> from t\closure.t and once from t\perlrun_extload.t):
>
> Prototype mismatch: sub
> ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_cmp:
> none vs ($$;$) at C:/apache2/perl5/lib/Exporter.pm line 65.
> at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
> Prototype mismatch: sub
> ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_is_equal:
> none vs ($$) at C:/apache2/perl5/lib/Exporter.pm line 65.
> at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
> Prototype mismatch: sub
> ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_filepath_cmp:
> none vs ($$;$) at C:/apache2/perl5/lib/Exporter.pm line 65.
> at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
Yup, it's because of the reload of the CODE which was deleted. I'm not
sure what can be done about these. Some time ago, I've spent a lot of
time trying to get rid of those, working with p5p, but it didn't work
out. The delete CODE refs (which we do in ModPerl::PerlRun) is as good
as it gets.
--
__________________________________________________________________
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Steve Hay <st...@uk.radan.com>.
Geoffrey Young wrote:
>Stas Bekman wrote:
>
>
>>Yesterday I've fixed the problems that were showstoppers for the _15
>>release. Any objections for doing it in the next few days?
>>
>>If there are none, any volunteers to do this release?
>>
>>We could get an RC right now, let it cook over the weekend and if
>>everything goes well release on Monday?
>>
>>
>
>in general I don't think much testing gets done over the weekend, so if
>you're serious about getting candidate results better to let it sit until
>tuesday so that people can test on monday (as the EU people have gone to the
>pub already today).
>
I would agree with that (being in the UK and knowing that I won't be
doing this stuff over the weekend (starting about now!) ;)
Just tried the latest CVS with 2.0.49 / 5.8.4 (I really must upgrade
them sometime too!):
Failed Test Stat Wstat Total Fail Failed List of Failed
-------------------------------------------------------------------------------
t\filter\out_bbs_filebucket.t 10 10 100.00% 1-10
t\hooks\authen_digest.t 7 1 14.29% 7
7 tests and 12 subtests skipped.
Failed 2/210 test scripts, 99.05% okay. 11/3691 subtests failed, 99.70%
okay.
(I also got "Scalars leaked: 1" twice from t\perl\ithreads.t)
More details separately.
ModPerl-Registry test all OK, but with these warnings twice over (once
from t\closure.t and once from t\perlrun_extload.t):
Prototype mismatch: sub
ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_cmp:
none vs ($$;$) at C:/apache2/perl5/lib/Exporter.pm line 65.
at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
Prototype mismatch: sub
ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_is_equal:
none vs ($$) at C:/apache2/perl5/lib/Exporter.pm line 65.
at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
Prototype mismatch: sub
ModPerl::ROOT::ModPerl::PerlRun::C_3a_Temp_modperl_2d2_2e0_ModPerl_2dRegistry_t_cgi_2dbin_closure_2epl::t_filepath_cmp:
none vs ($$;$) at C:/apache2/perl5/lib/Exporter.pm line 65.
at C:/Temp/modperl-2.0/ModPerl-Registry/t/cgi-bin/closure.pl line 5
- Steve
------------------------------------------------
Radan Computational Ltd.
The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: time for 1.99_15?
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
Stas Bekman wrote:
> Yesterday I've fixed the problems that were showstoppers for the _15
> release. Any objections for doing it in the next few days?
>
> If there are none, any volunteers to do this release?
>
> We could get an RC right now, let it cook over the weekend and if
> everything goes well release on Monday?
in general I don't think much testing gets done over the weekend, so if
you're serious about getting candidate results better to let it sit until
tuesday so that people can test on monday (as the EU people have gone to the
pub already today).
other than that +1 (and I guess that answers my A-T question as well :)
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org