perl 5.8.8 syslog tests failing on MacOS X (sometimes)
maddingue at free.fr
Fri Dec 15 15:05:02 GMT 2006
kane at dwim.org wrote:
> On Fri, Dec 15, 2006 at 12:57:43PM +0000, Edmund von der Burg wrote:
> > This is odd - and I think I know the cause but I want to check if
> > anyone else has seen it:
> > All tests successful, 50 subtests skipped.
> > Files=1, Tests=119, 1 wallclock secs ( 0.07 cusr + 0.03 csys = 0.10 CPU)
> > And then again a few seconds later:
> > ../ext/Sys/Syslog/t/syslog....ok 1/119
> > ../ext/Sys/Syslog/t/syslog....NOK 83# Failed test 'syslog() called
> > with level 'info''
> > # in ../ext/Sys/Syslog/t/syslog.t at line 108.
> > # got: 'no connection to syslog available
> > # - udp connect: nobody listening at
> > ../ext/Sys/Syslog/t/syslog.t line 107# '
> > # expected: ''
> > the test works / fails in roughly the same proportion.
> > My guess is that the tests should always be skipped, but that
> > occasionally the error being returned is not recognized as valid: ie
> > the 'udp connect' bit is unexpected.
> > Anyone confirm / deny this?
I've got a few reports of this but I'm usually unable to reproduce
it on my OSX with both blead and 5.8.8 IIRC. I'll try again in case
I've missed something.
> > If that is it I'll submit a patch and become immortal :)
If you can isolate the case and correct it, it will be appreciated :)
> Yup, it's happened to me too. Sebastien is aware of the issue, but
> unable to reproduce it. It seems sporadic failures, where one can't
> even predict if it will always be the 'first time after ./Configure'
> or 'after the last successful run' that it fails.
> I'm sure a patch would be appreciated, but always skipping the test
> seems the wrong way to go about this.
There are cases where it makes sense; for example the stream tests
usually fail on Linux and Cygwin, so I've added some skips there
(because stream is usually not implemented on those systems). But in
the case of the UDP failures on OSX, I suspect a bug in OSX or in the
way the UDP mechanism works. OTOH, stream and UDP are not the mechanisms
one should use: Sys::Syslog since version 0.15 supports native Unix
syslog(3) calls and will support Win32 event log in the next version
thanks to Yves Orton. You can test it from here:
Close the world, txEn eht nepO.
More information about the london.pm