Damn - nasty :( the problem is that the test failures on the linux
platforms are all genuine.
On 11/17/07, Daryl C. W. O'Shea [EMAIL PROTECTED] wrote:
The frequently failing buildbots need to be fixed (yeah I know, no ideas
from me), disabled or renamed (so that it's clear that they frequently
The frequently failing buildbots need to be fixed (yeah I know, no ideas
from me), disabled or renamed (so that it's clear that they frequently
fail) so that legit build failures actually get acted on.
It appears this one (and the jm-feisty one this time, although it
frequently fails for no
btw this is running Ubuntu Gutsy now. I really must try to track down
a test case to repro this bug outside of SpamAssassin...
--j.
[EMAIL PROTECTED] writes:
The Buildbot has detected a new failure of jm-feisty.
Full details are available at:
On Saturday September 15 2007 04:26:59 Daryl C. W. O'Shea wrote:
Mark Martinec wrote:
On Friday September 14 2007 22:27:59 Justin Mason wrote:
actually, I misremembered -- it's a speed thing.
http://www.ccl4.org/~nick/P/Fast_Enough/#needless_importing_is_slow
Probably not quite as
[EMAIL PROTECTED] writes:
The Buildbot has detected a new failure of mc-fast.
Full details are available at:
http://bbmass.spamassassin.org:8011/mc-fast/builds/893
Buildbot URL: http://bbmass.spamassassin.org:8011/
Buildslave for this Build: mc-fast
Build Reason:
Build Source
Justin,
[EMAIL PROTECTED] writes:
The Buildbot has detected a new failure of mc-fast.
Full details are available at:
http://bbmass.spamassassin.org:8011/mc-fast/builds/893
Undefined subroutine Mail::SpamAssassin::Conf::untaint_var
called at ... Mail/SpamAssassin/Conf.pm line 2843
Ok,
Mark Martinec writes:
Justin,
[EMAIL PROTECTED] writes:
The Buildbot has detected a new failure of mc-fast.
Full details are available at:
http://bbmass.spamassassin.org:8011/mc-fast/builds/893
Undefined subroutine Mail::SpamAssassin::Conf::untaint_var
called at ...
On Friday September 14 2007 22:27:59 Justin Mason wrote:
actually, I misremembered -- it's a speed thing.
http://www.ccl4.org/~nick/P/Fast_Enough/#needless_importing_is_slow
Probably not quite as relevant for our code as for POSIX.pm!
Right, a few milliseconds during a program startup,
once
Mark Martinec wrote:
On Friday September 14 2007 22:27:59 Justin Mason wrote:
actually, I misremembered -- it's a speed thing.
http://www.ccl4.org/~nick/P/Fast_Enough/#needless_importing_is_slow
Probably not quite as relevant for our code as for POSIX.pm!
Right, a few milliseconds during a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] schrieb:
The Buildbot has detected a new failure of mleisi-suse10.2-x86.
Full details are available at:
http://buildbot.spamassassin.org:8010/mleisi-suse10.2-x86/builds/150
Buildbot URL:
Matthias Leisi writes:
[EMAIL PROTECTED] schrieb:
The Buildbot has detected a new failure of mleisi-suse10.2-x86.
Full details are available at:
http://buildbot.spamassassin.org:8010/mleisi-suse10.2-x86/builds/150
Buildbot URL: http://buildbot.spamassassin.org:8010/
Buildslave
Daryl C. W. O'Shea writes:
[EMAIL PROTECTED] wrote:
The Buildbot has detected a new failure of mleisi-suse10.2-x86.
Full details are available at:
http://buildbot.spamassassin.org:8010/mleisi-suse10.2-x86/builds/100
Buildbot URL: http://buildbot.spamassassin.org:8010/
Buildslave
Buildslave for this Build: mleisi-suse10.2-x86
Build Reason:
Build Source Stamp: HEAD
Blamelist: dos
BUILD FAILED: failed test
sincerely,
-The Buildbot
Not sure what's causing this... I haven't touched trunk.
The two mleisi* buildbots seem to have a tendency to fail
[EMAIL PROTECTED] wrote:
The Buildbot has detected a new failure of mleisi-suse10.2-x86.
Full details are available at:
http://buildbot.spamassassin.org:8010/mleisi-suse10.2-x86/builds/100
Buildbot URL: http://buildbot.spamassassin.org:8010/
Buildslave for this Build: mleisi-suse10.2-x86
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
The Buildbot has detected a new failure of mleisi-suse10.2-x86.
Full details are available at:
http://buildbot.spamassassin.org:8010/mleisi-suse10.2-x86/builds/92
Buildbot URL: http://buildbot.spamassassin.org:8010/
[EMAIL PROTECTED] writes:
The Buildbot has detected a new failure of mleisi-suse10.2-x86.
Full details are available at:
http://buildbot.spamassassin.org:8010/mleisi-suse10.2-x86/builds/66
Buildbot URL: http://buildbot.spamassassin.org:8010/
Buildslave for this Build:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
Buildbot URL: http://buildbot.spamassassin.org:8010/
Buildslave for this Build: mleisi-suse10.2-x86_64
Build Reason: The web-page 'force build' button was pressed by '':
Build Source Stamp: HEAD
Blamelist:
[EMAIL PROTECTED] wrote, On 21/8/06 5:24 PM:
Blamelist: sidney
I didn't do it! :-)
It looks like something in mass check. The buildbot was started up after a
number of checkins had occurred, with one of mine in the 3.1 branch just
happening to be the most recent. Justin, you had some recent
Sidney Markowitz writes:
[EMAIL PROTECTED] wrote, On 21/8/06 5:24 PM:
Blamelist: sidney
I didn't do it! :-)
It looks like something in mass check. The buildbot was started up after a
number of checkins had occurred, with one of mine in the 3.1 branch just
happening to be the most recent.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
is this some kind of NAT problem? I notice it's affecting Sidney and
Michael's bots only.
Possibly, but it's also some sort of SVN is really down problem.
There also seems to be a mailer problem, multiple copies of
Sidney Markowitz [EMAIL PROTECTED] writes:
I'll look at that after I come back.
If you haven't already, could you disable the tests on any systems that
might fail between now and then? Thanks. :-)
Daniel
--
Daniel Quinlan
http://www.pathname.com/~quinlan/
On Sat, Dec 18, 2004 at 04:31:54PM +, Nix wrote:
don't multiply it by more than, say, ten. If SA goes fifty days without
a commit something is very wrong. :)
I know nothing about buildbot (haven't had time to look into it), but is there
some way the server can keep track of the commits, and
I had a power glitch here which rebooted the server. I think it happened
in the middle of the svn update causing all three slave jobs to fail,
and I think that it was a power glitch that caused the reboot. I'm not
going to bother to bring the buildbot slaves online again before I leave
on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
Justin Mason wrote:
(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...
I'm running three slaves on one machine, two of them on the same VMWare
virtual machine and
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:
On Fri, Dec 17, 2004 at 10:14:16AM -0800, Justin Mason wrote:
(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...
I don't think it's so much a dynamic-IP
Justin Mason wrote:
Sidney, have you tried setting --keepalive=300
I'll try that. What Michael says does make sense. I'm behind a NAT.
Is there a way of setting a port that the slave listens on? I can
configure my NAT to let the slaves be designated servers on some port if
I can make it a fixed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Justin Mason wrote:
Sidney, have you tried setting --keepalive=300
I'll try that. What Michael says does make sense. I'm behind a NAT.
Is there a way of setting a port that the slave listens on? I can
configure my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Malte S. Stretz wrote:
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?
The mass svn failure this morning was due to the svn server falling
over (ie kernel panic) and svn flat out wasn't available.
The ASF svn installation seems to be having some growing pains, you
might have noticed revision numbers jumping in orders of magnitudes,
there are now a good number of
Yuck, I don't know if --keepalive=300 is going to work. I added it
and now they disconnect after a few minutes of inactivity. I'm going
to shut my slaves off for now, I do enough local testing as it is, so
we'll just lose the FreeBSD machine.
Michael
pgprAmauhisNl.pgp
Description: PGP
On Fri, Dec 17, 2004 at 04:00:52PM -0600, Michael Parker wrote:
The mass svn failure this morning was due to the svn server falling
over (ie kernel panic) and svn flat out wasn't available.
The ASF svn installation seems to be having some growing pains, you
might have noticed revision
[EMAIL PROTECTED] (Justin Mason) writes:
Well, I think failed svn is something that all build failures produce.
Even if the problem is a bug, rather than an svn timeout...
I think we should remove (a) all of the NATed slaves and (b) any build
server that can't reliably connect to the server.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
Well, I think failed svn is something that all build failures produce.
Even if the problem is a bug, rather than an svn timeout...
I think we should remove (a) all of the NATed
On Fri, Dec 17, 2004 at 02:47:10PM -0800, Justin Mason wrote:
agreed, to be honest... Sidney, Michael, what do you think?
Already done.
Michael
pgpdN7ABuhutN.pgp
Description: PGP signature
Justin Mason wrote:
might be worth signing up to buildbot-devel (it's very low traffic)
and mention that...
I'm going away on holiday soon for a couple of weeks. I'll look at that
after I come back. There may be some issues to work out if I'm going to
test with their latest cvs version and
On Tue, Dec 14, 2004 at 09:58:56AM -0800, Justin Mason wrote:
oh btw I upgraded this to 0.6.2 yesterday, which is supposed
to handle NATted slaves better... sidney, michael, could
you try upgrading your slaves?
Yeah, I upgraded both of my slaves as well and it was still showing
the
On Thu, Dec 02, 2004 at 07:57:39AM -0800, [EMAIL PROTECTED] wrote:
The Buildbot has detected a new failure of trunk-parker-suse-9.2.
Buildbot URL: http://bugzilla.spamassassin.org:8010/
Build Reason: changes
Build Source Stamp: 26
Blamelist: felicity
BUILD FAILED: failed svn
I've noticed
On Thu, Dec 02, 2004 at 10:59:21AM -0500, Theo Van Dinter wrote:
On Thu, Dec 02, 2004 at 07:57:39AM -0800, [EMAIL PROTECTED] wrote:
The Buildbot has detected a new failure of trunk-parker-suse-9.2.
Buildbot URL: http://bugzilla.spamassassin.org:8010/
Build Reason: changes
Build Source
On Thursday 02 December 2004 17:06 CET Michael Parker wrote:
[...]
FYI, the FreeBSD failures are real (when they aren't the failed svn
type). For some odd reason, when running under buildbot, the
spamd_unix.t tests are failing. I can't recreate running outside of
buildbot, so I'm not sure
On Thu, Dec 02, 2004 at 07:11:48PM +0100, Malte S. Stretz wrote:
On Thursday 02 December 2004 17:06 CET Michael Parker wrote:
[...]
FYI, the FreeBSD failures are real (when they aren't the failed svn
type). For some odd reason, when running under buildbot, the
spamd_unix.t tests are
On Thursday 02 December 2004 21:01 CET Michael Parker wrote:
On Thu, Dec 02, 2004 at 07:11:48PM +0100, Malte S. Stretz wrote:
On Thursday 02 December 2004 17:06 CET Michael Parker wrote:
[...]
FYI, the FreeBSD failures are real (when they aren't the failed svn
type). For some odd
43 matches
Mail list logo
