Menu
▾
▴
log4perl-devel — Ongoing log4perl development
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(38) |
Sep
(126) |
Oct
(23) |
Nov
(72) |
Dec
(36) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(76) |
Feb
(32) |
Mar
(19) |
Apr
(6) |
May
(54) |
Jun
(40) |
Jul
(45) |
Aug
(35) |
Sep
(51) |
Oct
(67) |
Nov
(10) |
Dec
(50) |
| 2004 |
Jan
(51) |
Feb
(22) |
Mar
(22) |
Apr
(28) |
May
(53) |
Jun
(99) |
Jul
(38) |
Aug
(49) |
Sep
(23) |
Oct
(29) |
Nov
(30) |
Dec
(48) |
| 2005 |
Jan
(15) |
Feb
(21) |
Mar
(25) |
Apr
(16) |
May
(131) |
Jun
|
Jul
(8) |
Aug
(5) |
Sep
(15) |
Oct
|
Nov
(15) |
Dec
(12) |
| 2006 |
Jan
(15) |
Feb
(20) |
Mar
(8) |
Apr
(10) |
May
(3) |
Jun
(16) |
Jul
(15) |
Aug
(11) |
Sep
(17) |
Oct
(27) |
Nov
(11) |
Dec
(12) |
| 2007 |
Jan
(19) |
Feb
(18) |
Mar
(33) |
Apr
(4) |
May
(15) |
Jun
(22) |
Jul
(19) |
Aug
(20) |
Sep
(14) |
Oct
(4) |
Nov
(34) |
Dec
(11) |
| 2008 |
Jan
(8) |
Feb
(18) |
Mar
(2) |
Apr
(4) |
May
(26) |
Jun
(9) |
Jul
(8) |
Aug
(8) |
Sep
(3) |
Oct
(17) |
Nov
(14) |
Dec
(4) |
| 2009 |
Jan
(6) |
Feb
(41) |
Mar
(21) |
Apr
(10) |
May
(21) |
Jun
|
Jul
(8) |
Aug
(4) |
Sep
(3) |
Oct
(8) |
Nov
(6) |
Dec
(5) |
| 2010 |
Jan
(14) |
Feb
(13) |
Mar
(7) |
Apr
(12) |
May
(4) |
Jun
(1) |
Jul
(11) |
Aug
(5) |
Sep
|
Oct
(1) |
Nov
(10) |
Dec
|
| 2011 |
Jan
(7) |
Feb
(3) |
Mar
(1) |
Apr
(5) |
May
|
Jun
(1) |
Jul
(6) |
Aug
(6) |
Sep
(10) |
Oct
(5) |
Nov
(4) |
Dec
(5) |
| 2012 |
Jan
(4) |
Feb
(5) |
Mar
(1) |
Apr
(7) |
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
(5) |
Oct
(5) |
Nov
(4) |
Dec
(5) |
| 2013 |
Jan
(6) |
Feb
|
Mar
(14) |
Apr
(9) |
May
(3) |
Jun
(2) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(4) |
Dec
(6) |
| 2014 |
Jan
|
Feb
(1) |
Mar
(10) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(1) |
Nov
|
Dec
(4) |
| 2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: Roger P. <rog...@ea...> - 2003-02-05 12:04:59
|
Hi! I'm not on the mailing list (CC please) and the archive doesn't work. I'm having problems installing using ppm. I've tried to install 0.29 on two machines and they both failed. Installing 0.24 from http://theoryx5.uwinnipeg.ca/ppmpackages works tough. I get this error when using your repository: Error reading "http://log4perl.sourceforge.net/ppm/Log-Log4perl.tar.gz (See below for more info) Thanks! Roger P PPM interactive shell (2.1.5) - type 'help' for available commands. PPM> install "http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd" Install package '"http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd"?' (y/N): y Installing package '"http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd"'... Error installing package '"http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd" ': Error reading "http://log4perl.sourceforge.net/ppm/Log-Log4perl.tar.gz PPM> install "http://theoryx5.uwinnipeg.ca/ppmpackages/Log-Log4perl.ppd" Install package '"http://theoryx5.uwinnipeg.ca/ppmpackages/Log-Log4perl.ppd"?' ( y/N): y Installing package '"http://theoryx5.uwinnipeg.ca/ppmpackages/Log-Log4perl.ppd"' ... Bytes transferred: 28899 Installing D:\Perl\site\lib\Test\Builder.pm Installing D:\Perl\site\lib\Test\More.pm Installing D:\Perl\site\lib\Test\Simple.pm Installing D:\Perl\site\lib\Test\Tutorial.pod Writing D:\Perl\site\lib\auto\Test\Simple\.packlist Bytes transferred: 61710 Installing D:\Perl\html\site\lib\Log\Log4perl.html Installing D:\Perl\html\site\lib\Log\Log4perl\Appender.html Installing D:\Perl\html\site\lib\Log\Log4perl\Config.html Installing D:\Perl\html\site\lib\Log\Log4perl\JavaMap.html Installing D:\Perl\html\site\lib\Log\Log4perl\Level.html Installing D:\Perl\html\site\lib\Log\Log4perl\TestBuffer.html Installing D:\Perl\html\site\lib\Log\Log4perl\Layout\PatternLayout.html Installing D:\Perl\html\site\lib\Log\Log4perl\Layout\SimpleLayout.html Installing D:\Perl\html\site\lib\Log\Log4perl\JavaMap\ConsoleAppender.html Installing D:\Perl\html\site\lib\Log\Log4perl\JavaMap\FileAppender.html Installing D:\Perl\site\lib\Log\Log4perl.pm Installing D:\Perl\site\lib\Log\Log4perl\Appender.pm Installing D:\Perl\site\lib\Log\Log4perl\Config.pm Installing D:\Perl\site\lib\Log\Log4perl\DateFormat.pm Installing D:\Perl\site\lib\Log\Log4perl\JavaMap.pm Installing D:\Perl\site\lib\Log\Log4perl\Layout.pm Installing D:\Perl\site\lib\Log\Log4perl\Level.pm Installing D:\Perl\site\lib\Log\Log4perl\Logger.pm Installing D:\Perl\site\lib\Log\Log4perl\TestBuffer.pm Installing D:\Perl\site\lib\Log\Log4perl\Layout\PatternLayout.pm Installing D:\Perl\site\lib\Log\Log4perl\Layout\SimpleLayout.pm Installing D:\Perl\site\lib\Log\Log4perl\JavaMap\ConsoleAppender.pm Installing D:\Perl\site\lib\Log\Log4perl\JavaMap\FileAppender.pm Writing D:\Perl\site\lib\auto\Log\Log4perl\.packlist PPM> C:\>perl -v This is perl, v5.6.1 built for MSWin32-x86-multi-thread (with 1 registered patch, see perl -V for more detail) Copyright 1987-2001, Larry Wall Binary build 630 provided by ActiveState Tool Corp. http://www.ActiveState.com Built 20:29:41 Oct 31 2001 |
|
From: Mike S. <msc...@ao...> - 2003-02-03 18:47:45
|
wi...@da... wrote: >As best I can tell Log::Dispatch::RollingFile has been replaced by Log::Dispatch::FileRotate (granted there appear to be other new ones too)?? > > > Thanks for the note! I've updated the list in CVS, Log::Dispatch::FileRotate and Log::Log4perl::Appender::DBI have been added. The change will be part of 0.30. -- -- Mike Mike Schilli log...@pe... |
|
From: <msc...@ao...> - 2003-02-01 05:31:39
|
Hey there, Log::Log4perl friends, 0.29 has just been pushed to CPAN, quickly fixing the minor hickup 0.28 had -- sorry for the inconvenience! -- -- Mike ############################ # Mike Schilli # # log...@pe... # # http://perlmeister.com # # log4perl.sourceforge.net # ############################ |
|
From: Jim C. <jc...@di...> - 2003-02-01 00:39:39
|
Kevin Goess wrote:
> Thanks for the tip, Jim. I tried it, and then noticed that
> Data::Dumper is also not consistent about putting quotes around hash
> values. I'm only using it in the test, to see whether the data
> structures returned by the parsers PropertiesConfigurator and
> DOMConfigurator are the same for equivalent configs.
>
> In t/038XML-DOM1.t I ended up stealing some code from Data::Compare to
> diff the data structures, all this just so we wouldn't have a
> dependency on Data::Dump.
I guess I wasnt reading very carefully wrt why you were using it,
it reminded me of
============================================================
Log::Log4perl Recipe of the Week (#14):
in which case it might be appropriate, since sorted structures are
easier to eyeball for expected values,
and for diffs vs other copies of the same logfiles.
while were at it,
$Data::Dumper::Indent = 1;
is a 'better' format than the default: 2, which indents based on the
string-length of the keys, and can
thus look kinda ragged when a hash has
$h = { 'shortkeys' => [
1,
2
],
'really-long-key-names-which-result-in-data-sensitive-indents' => [
1,
2,
],
};
but, since that was a user recipe, and not a function, this might reduce
to Tip #14-a
|
|
From: Kevin G. <ke...@go...> - 2003-02-01 00:13:51
|
Thanks for the tip, Jim. I tried it, and then noticed that Data::Dumper is also not consistent about putting quotes around hash values. I'm only using it in the test, to see whether the data structures returned by the parsers PropertiesConfigurator and DOMConfigurator are the same for equivalent configs. In t/038XML-DOM1.t I ended up stealing some code from Data::Compare to diff the data structures, all this just so we wouldn't have a dependency on Data::Dump. Jim Cromie wrote: > Kevin Goess wrote: > >> >> Mike Schilli wrote: >> >>> Looks like this is related, >> >> >> >> Yeah, Data::Dumper doesn't always return data in the same order, darn it. > > > > $Data::Dumper::Sortkeys = 1; # alpha sort hash keys > > slows it down a bit, (never tested that - but it must), > but predictabilty is good in logs. > > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > log4perl-devel mailing list > log...@li... > https://lists.sourceforge.net/lists/listinfo/log4perl-devel -- Happy Trails . . . Kevin M. Goess (and Anne and Frank) 904 Carmel Ave. Albany, CA 94706 (510) 525-5217 |
|
From: Jim C. <jc...@di...> - 2003-01-31 23:36:07
|
Kevin Goess wrote: > > Mike Schilli wrote: > >> Looks like this is related, > > > Yeah, Data::Dumper doesn't always return data in the same order, darn it. $Data::Dumper::Sortkeys = 1; # alpha sort hash keys slows it down a bit, (never tested that - but it must), but predictabilty is good in logs. |
|
From: <Msc...@ao...> - 2003-01-31 20:33:01
|
In a message dated 1/31/03 11:40:36 AM Pacific Standard Time, ke...@go... writes: > Oh, I see, I thought it was a failure. Sure, leave it as it is. Ok, I've refreshed the webpage one more time with 0.29 -- I'm gonna run some tests tonight and if it looks ok, I'm gonna send it off to CPAN. Any hickups, let me know ... -- Mike Mike Schilli log...@pe... |
|
From: Kevin G. <ke...@go...> - 2003-01-31 19:36:23
|
> > It's not on CPAN yet. I'm not too happy with the change -- my > experiments just showed warnings, same warnings as you get when > installing Log::Dispatch. It wasn't breaking the test suite. Ok if we > leave 036JSyslog.t as it was for now? Oh, I see, I thought it was a failure. Sure, leave it as it is. -- Happy Trails . . . Kevin M. Goess (and Anne and Frank) 904 Carmel Ave. Albany, CA 94706 (510) 525-5217 |
|
From: <Msc...@ao...> - 2003-01-31 17:49:15
|
In a message dated 1/31/03 9:07:40 AM Pacific Standard Time, ke...@go... writes: > What was the final disposition of the 017Watch.t test? My position > would be that if we can't trust the timestamps on the filesystem, the > whole init_and_watch system is going to break down. There's two different things to consider: Initial offset and continuous drift. Without really having looked at the code, I would suspect that we could easily resolve the first item by determinining the offset the first time around. My concern was just that if you've got a file system that's a bit off (like the one I was using), the Log::Log4perl test suite will fail. This is not of immediate concern, though, I'll keep it on the TODO list. > And what was the final disposition of 036JSyslog.t? I just changed it > to always succeed. That way it won't keep log4perl from installing, but > it will give some indication to the user whether they can expecte syslog > logging to work on their system. I just did that right now, so you'll > need to update the web site (you didn't send to cpan yet, right?) It's not on CPAN yet. I'm not too happy with the change -- my experiments just showed warnings, same warnings as you get when installing Log::Dispatch. It wasn't breaking the test suite. Ok if we leave 036JSyslog.t as it was for now? -- Mike Mike Schilli log...@pe... |
|
From: Kevin G. <ke...@go...> - 2003-01-31 17:14:53
|
msc...@ao... wrote: > In a message dated 1/30/2003 8:00:07 PM Eastern Standard Time, Kevin > Goess <ke...@go...> writes: >> Umm, how do we test if the module isn't there? > > squirrel is your friend: > > http://www.perlmeister.com/scripts/squirrel-README.html > http://www.perlmeister.com/scripts/squirrel Ahh, I see what you're getting at. Very interesting. I'll see what I can do with that. -- Happy Trails . . . Kevin M. Goess (and Anne and Frank) 904 Carmel Ave. Albany, CA 94706 (510) 525-5217 |
|
From: Kevin G. <ke...@go...> - 2003-01-31 17:13:50
|
msc...@ao... wrote: > In a message dated 1/31/2003 1:58:03 AM Eastern Standard Time, > "Dintelmann, Peter" <Pet...@Dr...> writes: > >> I am looking for a feature similar to syslog's "last message >> repeated N times" in Log4perl. The intended use is for database >> connection modules and the like. > > Sounds like a very useful feature to me. However, I haven't seen it > anywhere in log4j's implementation, have you? > > Some random thoughts: > > The easiest way to implement it would probably be to have an appender > taking care of buffering (similar to what Log::Dispatch::Email does > now) and employing some logic to decide when to log (somewhat tricky, > because you can't buffer forever and if you don't flush before the > program ends, the messages are lost). My thoughts exactly, shouldn't be too hard for you to do. If you need a hint how to get started, you subclass Log::Dispatch::Output providing your own log_message() method, then reference your new subclass in the config like this: log4j.appender.appndr1 = My::Buffered::Appender log4j.appender.appndr1.layout = Log::Log4perl::Layout...whatever ...etc. -- Happy Trails . . . Kevin M. Goess (and Anne and Frank) 904 Carmel Ave. Albany, CA 94706 (510) 525-5217 |
|
From: Kevin G. <ke...@go...> - 2003-01-31 17:07:26
|
Msc...@ao... wrote:
>> Problem is that the CPAN release needs a new version number.
>
> Never mind, I got confused :). I've just release 0.29 to the web
> site, based on your branch.
There ya go! That's what I was getting at.
What was the final disposition of the 017Watch.t test? My position
would be that if we can't trust the timestamps on the filesystem, the
whole init_and_watch system is going to break down. We wouldn't be able
to do
if ( ($LAST_CHECKED_AT + $WATCH_DELAY) < time()){
because there's no relation between time() and stat($FILE_TO_WATCH).
Instead of calling time(), you'd have to touch a file on the filesystem,
in effect asking the filesystem what time *it* thinks it is now.
So I think we should leave 036JSyslog.t as it is. Drifing times on an
NFS mount should actually cause a failure (they'll bollix other things
to, like tar for instance--ntp synchronization is a very good idea for
NFS situations ).
And what was the final disposition of 036JSyslog.t? I just changed it
to always succeed. That way it won't keep log4perl from installing, but
it will give some indication to the user whether they can expecte syslog
logging to work on their system. I just did that right now, so you'll
need to update the web site (you didn't send to cpan yet, right?)
> Please verify and merge your stuff to the
> tip.
Done! But I'll wait till the end of the day to check it in.
--
Happy Trails . . .
Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA 94706
(510) 525-5217
|
|
From: <msc...@ao...> - 2003-01-31 16:16:50
|
In a message dated 1/31/2003 1:58:03 AM Eastern Standard Time, "Dintelmann, Peter" <Pet...@Dr...> writes: >I am looking for a feature similar to syslog's "last message repeated N >times" in Log4perl. The intended use is for database connection modules >and the like. Sounds like a very useful feature to me. However, I haven't seen it anywhere in log4j's implementation, have you? Some random thoughts: The easiest way to implement it would probably be to have an appender taking care of buffering (similar to what Log::Dispatch::Email does now) and employing some logic to decide when to log (somewhat tricky, because you can't buffer forever and if you don't flush before the program ends, the messages are lost). On the other hand, this feature is generic enough to put it into some kind of (yet to be implemented) "output filter" which could be plugged between log4perl and any appender. Also, it could be implemented differently for sequential and random access appenders. In case of a database, you could just keep writing to the same row and increasing a count, while in case of a file appender, you'd have to have some external buffering with flush parameters. Thoughts anybody? -- -- Mike ############################ # Mike Schilli # # log...@pe... # # http://perlmeister.com # # log4perl.sourceforge.net # ############################ |
|
From: <msc...@ao...> - 2003-01-31 16:09:38
|
forwarded ... |
|
From: <Msc...@ao...> - 2003-01-31 05:20:46
|
In a message dated 1/30/2003 11:38:50 PM Eastern Standard Time, msc...@ao... writes: >Problem is that the CPAN release needs a new version number. Never mind, I got confused :). I've just release 0.29 to the web site, based on your branch. Please verify and merge your stuff to the tip. -- Mike ############################ # Mike Schilli # # log...@pe... # # http://perlmeister.com # # log4perl.sourceforge.net # ############################ |
|
From: <msc...@ao...> - 2003-01-31 04:39:06
|
In a message dated 1/30/2003 8:00:07 PM Eastern Standard Time, Kevin Goess <ke...@go...> writes:
>But I already checked a bunch of other work I'm doing on the XML-DOM
>into 0.29 which isn't ready to be released yet. Just to this in your
Problem is that the CPAN release needs a new version number. We can't re-release 0.28. One option would be to call it 0.281 but that's a risky thing to do on CPAN, that could break all kinds of things (ordering etc.). Can't you revert your checkins so we get a clean 0.29 real quick?
>Umm, how do we test if the module isn't there?
squirrel is your friend:
http://www.perlmeister.com/scripts/squirrel-README.html
http://www.perlmeister.com/scripts/squirrel
--
-- Mike
############################
# Mike Schilli #
# log...@pe... #
# http://perlmeister.com #
# log4perl.sourceforge.net #
############################
|
|
From: Mike S. <msc...@ao...> - 2003-01-31 01:12:02
|
BTW, the error with the scewed NFS time is quite severe. If someone installs Log::Log4perl on a NFS-based file system and the clocks are off by a few seconds, Log::Log4perl won't pass its test suite. I think the problem is that we rely on the fact that the system time (obtained via time()) and the file system's -M date are in sync. Wouldn't it be safer to store the -M time of the config file as soon as it has been written instead of using time() for config_and_watch? -- -- Mike Mike Schilli m...@pe... |
|
From: Mike S. <msc...@ao...> - 2003-01-31 01:07:44
|
ke...@go... wrote: > > t/036JSyslog.........unix passed to setlogsock, but path not > available > at > /u/mschilli/PERL580/bin/perl/lib/site_perl/5.8.0/Log/Dispatch/Syslog.pm > line 66 > > Can you run this > perl -Iblib/lib t/036JSyslog.t > and send the output? I'm thinking Sys::Syslog has problems, maybe we > should turn off the test. > > Just verified that you get the same error when you install Log::Dispatch on Solaris. So the warning is not related to Log::Log4perl. -- -- Mike Mike Schilli m...@pe... |
|
From: Kevin G. <ke...@go...> - 2003-01-31 01:00:14
|
>> Since CPAN doesn't allow for updating the same version, we should >> probably just go ahead and prepare 0.29 right away.Want to roll in your >> >> See my earlier email, the CVS branch rel-0-28 is releasable. > > Can you check it into 0.29? That's easier for me to handle. But I already checked a bunch of other work I'm doing on the XML-DOM into 0.29 which isn't ready to be released yet. Just to this in your cvs directory cvs update -r rel-0-28 to change your sources to the branch, do the release, and when you're finished you can do cvs update -A to switch your sources back to the main trunk. If you're using kde, cervisia is a cvs front-end with a nice tree-browsing feature that lets you see what's going on. > >> Longer term, I think we also need to run tests for the different cases >> of optional modules being present or absent. >> >> Eh? I don't follow you? > > I just meant we need to test both cases, with and without the optional > modules present. Umm, how do we test if the module isn't there? I think the tests and code are pretty well modularized, if some optional piece (like Win32::EventLog) is missing it doesn't affect anything else. -- Happy Trails . . . Kevin M. Goess (and Anne and Frank) 904 Carmel Ave. Albany, CA 94706 (510) 525-5217 |
|
From: Kevin G. <ke...@go...> - 2003-01-31 00:53:07
|
> t/036JSyslog.........unix passed to setlogsock, but path not available > at /u/mschilli/PERL580/bin/perl/lib/site_perl/5.8.0/Log/Dispatch/Syslog.pm line 66 Can you run this perl -Iblib/lib t/036JSyslog.t and send the output? I'm thinking Sys::Syslog has problems, maybe we should turn off the test. -- Happy Trails . . . Kevin M. Goess (and Anne and Frank) 904 Carmel Ave. Albany, CA 94706 (510) 525-5217 |
|
From: Mark B. <md...@ji...> - 2003-01-31 00:40:00
|
>> On Thu, 30 Jan 2003 13:35:05 -0800,
>> Mike Schilli(M) wrote:
M> msc...@ao... wrote:
M> Hmm ... all kinds of weird stuff happening on Solaris:
Which version?
On,
$ uname -a
SunOS xxxxxx 5.6 Generic_105181-11 sun4u sparc
It looks mostly OK to me:
PERL_DL_NONLAZY=1 /tmp/.zzzzzzzzzzDummyLongPathToRelocatezzzzzzzPerl/bin/perl -Iblib/arch -Iblib/lib -I/tmp/.zzzzzzzzzzDummyLongPathToRelocatezzzzzzzPerl/lib/perl5/5.6.1/sun4-solaris -I/tmp/.zzzzzzzzzzDummyLongPathToRelocatezzzzzzzPerl/lib/perl5/5.6.1 -e 'use Test::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;' t/*.t
t/001Level..........ok
t/002Logger.........ok
t/003Layout.........ok
t/004Config.........ok
t/005Config-Perl....ok
t/006Config-Java....ok
t/007LogPrio........ok
t/008ConfCat........ok
t/009Deuce..........ok
t/010JConsole.......Possible attempt to separate words with commas at t/010JConsole.t line 9.
ok
t/011JFile..........Possible attempt to separate words with commas at t/011JFile.t line 6.
ok
t/012Deeper.........ok
t/013Bench..........ok
t/014ConfErrs.......ok
t/015fltmsg........."my" variable $app masks earlier declaration in same scope at t/015fltmsg.t line 46.
"my" variable $app masks earlier declaration in same scope at t/015fltmsg.t line 65.
"my" variable $app masks earlier declaration in same scope at t/015fltmsg.t line 83.
"my" variable $app masks earlier declaration in same scope at t/015fltmsg.t line 108.
ok
t/016Export.........ok
t/017Watch..........ok
t/018Init...........ok
t/019Warn...........ok
t/020Easy...........ok
t/021AppThres.......ok
t/022Wrap...........ok
t/023Date...........ok
t/024WarnDieCarp....ok
t/025CustLevels.....ok
t/026FileApp........ok
t/027Watch2.........ok
t/028Additivity.....ok
t/029SysWide........ok
t/030LDLevel........ok
t/031NDC............ok
t/032JRollFile......Log::Dispatch::FileRotate not installed, skipping...
ok
t/033UsrCspec.......ok
t/034DBI............DBD::CSV not installed, skipping tests
ok
t/035JDBCAppender...DBD::CSV not installed, skipping tests
ok
t/036JSyslog........ok
t/037JWin32Event....Log::Dispatch::Win32EventLog not installed, skipping..
ok
t/038XML-DOM1.......XML::DOM not installed, skipping tests
ok
All tests successful.
Files=38, Tests=343, 34 wallclock secs (18.59 cusr + 2.46 csys = 21.05 CPU)
Using,
$ perl -V
Summary of my perl5 (revision 5.0 version 6 subversion 1) configuration:
Platform:
osname=solaris, osvers=2.6, archname=sun4-solaris
uname='sunos xxxxxx 5.6 generic_105181-11 sun4u sparc '
config_args='-d'
hint=previous, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef
useperlio=undef d_sfio=undef uselargefiles=undef usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
Compiler:
cc='gcc', ccflags ='-fno-strict-aliasing -I/usr/local/include -I/opt/local/include -I/opt/gnu/include',
optimize='-O',
cppflags='-fno-strict-aliasing -I/usr/local/include -I/opt/local/include -I/opt/gnu/include'
ccversion='', gccversion='2.95.3 20010315 (release)', gccosandvers='solaris2.6'
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=4
alignbytes=8, usemymalloc=y, prototype=define
Linker and Libraries:
ld='gcc', ldflags =' -L/usr/local/lib -L/opt/local/lib -L/opt/gnu/lib'
libpth=/usr/local/lib /opt/local/lib /opt/gnu/lib /usr/lib /usr/ccs/lib
libs=-lsocket -lnsl -ldl -lm -lc
perllibs=-lsocket -lnsl -ldl -lm -lc
libc=/usr/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' '
cccdlflags='-fPIC', lddlflags='-G -L/usr/local/lib -L/opt/local/lib -L/opt/gnu/lib'
Characteristics of this binary (from libperl):
Compile-time options:
Built under solaris
Compiled at Oct 16 2002 17:58:15
@INC:
/tmp/.zzzzzzzzzzDummyLongPathToRelocatezzzzzzzPerl/lib/perl5/5.6.1/sun4-solaris
/tmp/.zzzzzzzzzzDummyLongPathToRelocatezzzzzzzPerl/lib/perl5/5.6.1
/tmp/.zzzzzzzzzzDummyLongPathToRelocatezzzzzzzPerl/lib/perl5/site_perl/5.6.1/sun4-solaris
/tmp/.zzzzzzzzzzDummyLongPathToRelocatezzzzzzzPerl/lib/perl5/site_perl/5.6.1
/tmp/.zzzzzzzzzzDummyLongPathToRelocatezzzzzzzPerl/lib/perl5/site_perl
/tmp/.zzzzzzzzzzDummyLongPathToRelocatezzzzzzzPerl/lib/site_perl/5.6.0/sun4-solaris
/tmp/.zzzzzzzzzzDummyLongPathToRelocatezzzzzzzPerl/lib/site_perl/5.6.0
.
|
|
From: Mike S. <msc...@ao...> - 2003-01-30 21:24:37
|
msc...@ao... wrote:
> ke...@go... wrote:
>
>>
>> I don't have access to a solaris box, the problem looks like it's in
>> Log::Dispatch::Syslog, it might have to do with the individual system
>> setup. We could just take the test out, but on the other hand it
>> might be telling us something useful here. I'm not sure what to
>> do--what do you think?
>
>
> I'll try with a Solaris box ... and is the Log::Dispatch::Syslog test
> case new in 0.28?
Hmm ... all kinds of weird stuff happening on Solaris:
t/001Level...........ok
t/002Logger..........ok
t/003Layout..........ok
t/004Config..........ok
t/005Config-Perl.....ok
t/006Config-Java.....ok
t/007LogPrio.........ok
t/008ConfCat.........ok
t/009Deuce...........ok
t/010JConsole........ok
t/011JFile...........ok
t/012Deeper..........ok
t/013Bench...........ok
t/014ConfErrs........ok
t/015fltmsg..........ok
t/016Export..........ok
t/017Watch...........# Test 1 got: 'INFO - info message
INFO - 2nd info message
INFO - 2nd info message again
' (t/017Watch.t at line 74)
# Expected: 'INFO - info message
DEBUG animal.dog - 2nd debug message
INFO animal.dog - 2nd info message
INFO animal.dog - 2nd info message again
'
t/017Watch...........NOK 1# Test 2 got: 'INFO - info message
INFO - 2nd info message
INFO - 2nd info message again
INFO - 3rd info message
' (t/017Watch.t at line 105)
# Expected: 'INFO - info message
DEBUG animal.dog - 2nd debug message
INFO animal.dog - 2nd info message
INFO animal.dog - 2nd info message again
INFO - 3rd info message
'
t/017Watch...........FAILED tests
1-2
Failed 2/2 tests, 0.00% okay
t/018Init............ok
t/019Warn............ok
t/020Easy............ok
t/021AppThres........ok
t/022Wrap............ok
t/023Date............ok
t/024WarnDieCarp.....ok
t/025CustLevels......ok
t/026FileApp.........ok
t/027Watch2..........NOK 2# Test 2 got: 'DEBUG - debug message, should
appear
DEBUG - debug message, should NOT appear
' (t/027Watch2.t at line 79)
# Expected: ''
t/027Watch2..........NOK 3# Test 3 got: 'DEBUG - debug message, should
appear
DEBUG - debug message, should NOT appear
WARN - warning message, should appear
' (t/027Watch2.t at line 83)
# Expected: 'WARN - warning message, should appear
'
t/027Watch2..........FAILED tests
2-3
Failed 2/5 tests, 60.00% okay
t/028Additivity......ok
t/029SysWide.........ok
t/030LDLevel.........ok
t/031NDC.............ok
t/032JRollFile.......ok 1/1Log::Dispatch::FileRotate not installed,
skipping...
t/032JRollFile.......ok
t/033UsrCspec........ok
t/034DBI.............DBD::CSV not installed, skipping tests
t/034DBI.............ok
t/035JDBCAppender....DBD::CSV not installed, skipping tests
t/036JSyslog.........unix passed to setlogsock, but path not available
at
/u/mschilli/PERL580/bin/perl/lib/site_perl/5.8.0/Log/Dispatch/Syslog.pm
line 66
t/036JSyslog.........ok
t/037JWin32Event.....Log::Dispatch::Win32EventLog not installed, skipping..
t/037JWin32Event.....ok
t/038XML-DOM1........XML::DOM not installed, skipping tests
t/038XML-DOM1........ok
t/039XML-DOM2........XML::DOM not installed, skipping tests
t/039XML-DOM2........ok
-- Mike
Mike Schilli
log...@pe...
|
|
From: Mike S. <msc...@ao...> - 2003-01-30 21:10:06
|
ke...@go... wrote: > > I don't have access to a solaris box, the problem looks like it's in > Log::Dispatch::Syslog, it might have to do with the individual system > setup. We could just take the test out, but on the other hand it might > be telling us something useful here. I'm not sure what to do--what do > you think? I'll try with a Solaris box ... and is the Log::Dispatch::Syslog test case new in 0.28? > Since CPAN doesn't allow for updating the same version, we should > probably just go ahead and prepare 0.29 right away.Want to roll in your > > See my earlier email, the CVS branch rel-0-28 is releasable. Can you check it into 0.29? That's easier for me to handle. > Longer term, I think we also need to run tests for the different cases > of optional modules being present or absent. > > Eh? I don't follow you? I just meant we need to test both cases, with and without the optional modules present. -- -- Mike Mike Schilli log...@pe... |
|
From: Kevin G. <ke...@go...> - 2003-01-30 19:14:50
|
Kevin Goess wrote: > Mike Schilli wrote: > >> can you also please check the other warning with syslog shown below? > > >> t/036JSyslog.........unix passed to setlogsock, but path not available > >> at /usr/local/perl/lib/site_perl/5.8.0/Log/Dispatch/Syslog.pm line 66 > > I don't have access to a solaris box, the problem looks like it's in > Log::Dispatch::Syslog, it might have to do with the individual system > setup. We could just take the test out, but on the other hand it might > be telling us something useful here. I'm not sure what to do--what do > you think? On the other hand, it looks like Log::Dispatch has seen problems here, stemming from Sys::Syslog: http://testers.cpan.org/search?request=dist&dist=Log-Dispatch How about I disable the test but leave it in there to help people diagnose problems if they want to use it? -- Happy Trails . . . Kevin M. Goess (and Anne and Frank) 904 Carmel Ave. Albany, CA 94706 (510) 525-5217 |
|
From: Kevin G. <ke...@go...> - 2003-01-30 18:54:58
|
Mike Schilli wrote: > Looks like this is related, Yeah, Data::Dumper doesn't always return data in the same order, darn it. My changes to the rel-0-28 branch will fix the failure of 038XML-DOM1.t. > can you also please check the other warning > with syslog shown below? >> t/036JSyslog.........unix passed to setlogsock, but path not available >> at /usr/local/perl/lib/site_perl/5.8.0/Log/Dispatch/Syslog.pm line 66 I don't have access to a solaris box, the problem looks like it's in Log::Dispatch::Syslog, it might have to do with the individual system setup. We could just take the test out, but on the other hand it might be telling us something useful here. I'm not sure what to do--what do you think? > Since CPAN doesn't allow for updating the same version, we should > probably just go ahead and prepare 0.29 right away.Want to roll in your > patch into the tip? It's no biggie if we fix it real soon. See my earlier email, the CVS branch rel-0-28 is releasable. > Longer term, I think we also need to run tests for the different cases > of optional modules being present or absent. Eh? I don't follow you? -- Happy Trails . . . Kevin M. Goess (and Anne and Frank) 904 Carmel Ave. Albany, CA 94706 (510) 525-5217 |
139 messages has been excluded from this view by a project administrator.
