perl 5.8.8 syslog tests failing on MacOS X (sometimes)

[Edmund von der Burg]

This is odd - and I think I know the cause but I want to check if
anyone else has seen it:

evdb at cindy ~/cdb/ext/build/perl-5.8.8/t $ ./perl harness
../ext/Sys/Syslog/t/syslog.t
../ext/Sys/Syslog/t/syslog....ok
        50/119 skipped: various reasons
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:

evdb at cindy ~/cdb/ext/build/perl-5.8.8/t $ ./perl harness
../ext/Sys/Syslog/t/syslog.t
../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: ''

#   Failed test 'syslog() should return true: '0''
../ext/Sys/Syslog/t/syslog....NOK 84#   in
../ext/Sys/Syslog/t/syslog.t at line 109.

#   Failed test 'syslog() called with level 'info''
../ext/Sys/Syslog/t/syslog....NOK 85#   in
../ext/Sys/Syslog/t/syslog.t at line 113.
#          got: 'no connection to syslog available
#       - udp connect: nobody listening at
../ext/Sys/Syslog/t/syslog.t line 112# '
#     expected: ''

#   Failed test 'syslog() should return true: '0''
../ext/Sys/Syslog/t/syslog....NOK 86#   in
../ext/Sys/Syslog/t/syslog.t at line 114.
# Looks like you failed 4 tests of 119.
../ext/Sys/Syslog/t/syslog....dubious
        Test returned status 4 (wstat 1024, 0x400)
DIED. FAILED tests 83-86
        Failed 4/119 tests, 96.64% okay (less 38 skipped tests: 77
okay, 64.71%)Failed Test                  Stat Wstat Total Fail
Failed  List of Failed
-------------------------------------------------------------------------------
../ext/Sys/Syslog/t/syslog.t    4  1024   119    4   3.36%  83-86
38 subtests skipped.
Failed 1/1 test scripts, 0.00% okay. 4/119 subtests failed, 96.64% okay.


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?

If that is it I'll submit a patch and become immortal :)

Cheers,
  Edmund.


-- 
In reality I'm evdb at ecclestoad.co.uk - http://ecclestoad.co.uk