Re: [log4perl-devel] Re: FAIL Log-Log4perl-0.28 sun4-solaris 2.8

[<Msc...@ao...>]

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...