They are probably worth paying attention to -- generally, there is a bug there ;)
I think there's some kind of bug with spamd on that version of Solaris where it's holding onto the socket for too long. Alternately, it could just be a bug in the test suite itself (which is certainly more common). --j. Daryl C. W. O'Shea writes: > Do we know what's causing the spamd test to (often) attempt a bind to a > port that's already in use? I stopped paying attention to build > failures long ago now. > > Daryl > > > [20057] error: spamd: could not create INET socket on 127.0.0.1:52821: > Address already in use > spamd: could not create INET socket on 127.0.0.1:52821: Address already > in use > > > [20502] error: spamd: could not create INET socket on 127.0.0.1:53266: > Address already in use > spamd: could not create INET socket on 127.0.0.1:53266: Address already > in use > > > On 25/03/2008 7:08 PM, Apache Hudson Server wrote: > > See http://hudson.zones.apache.org/hudson/job/SpamAssassin-trunk/511/changes > > > >
