On Friday 17 December 2004 19:14 CET Justin Mason wrote:
> Malte S. Stretz writes:
> > On Friday 17 December 2004 11:36 CET [EMAIL PROTECTED]
> >
> > wrote:
> > > The Buildbot has detected a new failure of trunk-debian-stable.
> > >
> > > Buildbot URL: http://bugzilla.spamassassin.org:8010/
> > >
> > > Build Reason: changes
> > > Build Source Stamp: 112
> > > Blamelist: quinlan
> > >
> > > BUILD FAILED: failed svn
> >
> > Those messages are getting a bit annoying, is there any way to filter
> > any builtbot message which contains "BUILD FAILED: failed svn" on the
> > server?
>
> no!
>
> (a) they really are failures. in this case the svn server seems to have
> died, which is good to know ;) The whole point of this is to get
> notification of failures.
Hm, if the svn update failed, it's most probably an infra problem or
something with the buildbot's uplink, something we can't fix anyway and
which will probably go away by itself. At least nothing we need a whole
load of notifies of (the maintainer of the buldbot in question should of
course get a notice). IMO :) But I guess I'll just filter those messages
locally.
> (b) however the -parker- and -sidney- ones *are* getting annoying. ;) I
> suggest we turn off those slaves until we can figure out how to get
> buildbot to work with dynamic-IP slaves...
Does anybody know what exactly goes wrong? Maybe it could work if we use
port forwarding or stunnel or something to route the traffic to the dynamic
clients over some server with a static IP?
Cheers,
Malte
--
[SGT] Simon G. Tatham: "How to Report Bugs Effectively"
<http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>
[ESR] Eric S. Raymond: "How To Ask Questions The Smart Way"
<http://www.catb.org/~esr/faqs/smart-questions.html>
