You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@spamassassin.apache.org by Apache Hudson Server <hu...@hudson.zones.apache.org> on 2008/03/26 00:08:04 UTC

Hudson build became unstable: SpamAssassin-trunk #511

See http://hudson.zones.apache.org/hudson/job/SpamAssassin-trunk/511/changes

Hudson build is back to stable: SpamAssassin-trunk #512

Posted by Apache Hudson Server <hu...@hudson.zones.apache.org>.

See http://hudson.zones.apache.org/hudson/job/SpamAssassin-trunk/512/changes

Hudson Build Failures (Re: Hudson build became unstable: SpamAssassin-trunk #511)

Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.

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