[Buildbot-devel] buildmaster almost starts, but doesn't really

Wed Sep 5 19:41:06 UTC 2007

I'm trying to get 0.7.5 going, and I have what I think is a reasonable 
master.cfg. But something must be wrong, because it never finishes starting:

[root at asimov Buildbot]# buildbot restart ~/Buildbot/
buildbot process 21680 is dead
now restarting buildbot process..
Following twistd.log until startup finished..
2007/09/05 15:05 -0400 [-] Log opened.
2007/09/05 15:05 -0400 [-] twistd 2.5.0 (/usr/bin/python 2.4.2) starting up
2007/09/05 15:05 -0400 [-] reactor class: <class 
'twisted.internet.selectreactor.SelectReactor'>
2007/09/05 15:05 -0400 [-] Loading buildbot.tac...
2007/09/05 15:05 -0400 [-] Loaded.
2007/09/05 15:05 -0400 [-] loading configuration from 
/home/dtodd/Buildbot/master.cfg
2007/09/05 15:05 -0400 [-] twisted.conch.manhole_ssh.ConchFactory 
starting on 9999
2007/09/05 15:05 -0400 [-] Starting factory 
<twisted.conch.manhole_ssh.ConchFactory instance at 0xb79f10cc>
2007/09/05 15:05 -0400 [-] Manhole listening via SSH on port 
tcp:9999:interface=127.0.0.1
2007/09/05 15:05 -0400 [-] adding new builder componentFramework for 
category None
2007/09/05 15:05 -0400 [-] trying to load status pickle from 
/home/dtodd/Buildbot/full/builder
2007/09/05 15:05 -0400 [-] added builder componentFramework in category None
2007/09/05 15:05 -0400 [-] adding IStatusReceiver <Waterfall on port 
tcp:8010>
2007/09/05 15:05 -0400 [-] twisted.web.server.Site starting on 8010
2007/09/05 15:05 -0400 [-] Starting factory <twisted.web.server.Site 
instance at 0xb790b66c>
2007/09/05 15:05 -0400 [-] BuildMaster listening on port tcp:9989
2007/09/05 15:05 -0400 [-] configuration update started
2007/09/05 15:05 -0400 [-] Unhandled error in Deferred:

The buildmaster took more than 5 seconds to start, so we were unable to
confirm that it started correctly. Please 'tail twistd.log' and look for a
line that says 'configuration update complete' to verify correct startup.

We never get to "configuration update complete"

Help?

master.cfg:

# -*- python -*-
# ex: set syntax=python:

# This is a sample buildmaster config file. It must be installed as
# 'master.cfg' in your buildmaster's base directory (although the filename
# can be changed with the --basedir option to 'mktap buildbot master').

# It has one job: define a dictionary named BuildmasterConfig. This
# dictionary has a variety of keys to control different aspects of the
# buildmaster. They are documented in docs/config.xhtml .

# This is the dictionary that the buildmaster pays attention to. We also use
# a shorter alias to save typing.
c = BuildmasterConfig = {}

####### BUILDSLAVES

# the 'bots' list defines the set of allowable buildslaves. Each element 
is a
# tuple of bot-name and bot-password. These correspond to values given 
to the
# buildslave's mktap invocation.
c['bots'] = [("irobot", "irobot")]

# 'slavePortnum' defines the TCP port to listen on. This must match the 
value
# configured into the buildslaves (with their --master option)

c['slavePortnum'] = 9989

####### CHANGESOURCES

# the 'sources' list tells the buildmaster how it should find out about
# source code changes. Any class which implements IChangeSource can be added
# to this list: there are several in buildbot/changes/*.py to choose from.

c['sources'] = []

# For example, if you had CVSToys installed on your repository, and your
# CVSROOT/freshcfg file had an entry like this:
#pb = ConfigurationSet([
#    (None, None, None, PBService(userpass=('foo', 'bar'), port=4519)),
#    ])

from buildbot.changes.freshcvs import FreshCVSSourceNewcred

s = FreshCVSSourceNewcred(host="cvs.wardrobe.irobot.com", port=4519,
                               user="irobot", passwd="aware",
                               prefix="Twisted/")
c['sources'] = [s]

# then you could use the following buildmaster Change Source to subscribe to
# the FreshCVS daemon and be notified on every commit:
#
#from buildbot.changes.freshcvs import FreshCVSSource
#fc_source = FreshCVSSource("cvs.example.com", 4519, "foo", "bar")
#c['sources'].append(fc_source)

# or, use a PBChangeSource, and then have your repository's commit 
script run
# 'buildbot sendchange', or contrib/svn_buildbot.py, or
# contrib/arch_buildbot.py :
#
#from buildbot.changes.pb import PBChangeSource
#c['sources'].append(PBChangeSource())

####### SCHEDULERS

## configure the Schedulers

from buildbot.scheduler import Scheduler
c['schedulers'] = []
c['schedulers'].append(Scheduler(name="all", branch=None,
                                 treeStableTimer=2*60,
                                 builderNames=["componentFramework"]))
from buildbot.scheduler import Try_Jobdir
c['schedulers'].append(Try_Jobdir("basic", 
["componentFramework"],jobdir="jobdir"))

####### BUILDERS

# the 'builders' list defines the Builders. Each one is configured with a
# dictionary, using the following keys:
#  name (required): the name used to describe this bilder
#  slavename (required): which slave to use, must appear in c['bots']
#  builddir (required): which subdirectory to run the builder in
#  factory (required): a BuildFactory to define how the build is run
#  periodicBuildTime (optional): if set, force a build every N seconds

# buildbot/process/factory.py provides several BuildFactory classes you can
# start with, which implement build processes for common targets (GNU
# autoconf projects, CPAN perl modules, etc). The factory.BuildFactory 
is the
# base class, and is configured with a series of BuildSteps. When the build
# is run, the appropriate buildslave is told to execute each Step in turn.

# the first BuildStep is typically responsible for obtaining a copy of the
# sources. There are source-obtaining Steps in buildbot/process/step.py for
# CVS, SVN, and others.

cvsroot = ":pserver:dtodd at cvs.wardrobe.irobot.com:/usr/local/cvsroot"
cvsmodule = "gni/buildtools/aware2build"

builders = []

from buildbot.process import factory
from buildbot.steps.source import CVS
from buildbot.steps.shell import Compile
f1 = factory.BuildFactory()
f1.addStep(CVS,
           cvsroot=cvsroot, cvsmodule=cvsmodule, login="dtodd",
           mode="copy")
f1.addStep(Compile, command=["aware2build", "build_42 build_44 linux-x86 
gni/aware/code/componentFramework"])

b1 = {'name': "componentFramework",
      'slavename': "irobot",
      'builddir': "full",
      'factory': f1,
      }
c['builders'] = [b1]

####### STATUS TARGETS

# 'status' is a list of Status Targets. The results of each build will be
# pushed to these targets. buildbot/status/*.py has a variety to choose 
from,
# including web pages, email senders, and IRC bots.

c['status'] = []

from buildbot.status import html
c['status'].append(html.Waterfall(http_port=8010))

# from buildbot.status import mail
# 
c['status'].append(mail.MailNotifier(fromaddr="buildbot at asimov.wardrobe.irobot.com",
#                                      extraRecipients=["dtodd at irobot.com"],
#                                      sendToInterestedUsers=False))
#
# from buildbot.status import words
# c['status'].append(words.IRC(host="leprosy.wardrobe.irobot.com", 
nick="buildbot",
#                              channels=["#buildbot"]))
#
# from buildbot.status import client
# c['status'].append(client.PBListener(9988))

####### DEBUGGING OPTIONS

# if you set 'debugPassword', then you can connect to the buildmaster with
# the diagnostic tool in contrib/debugclient.py . From this tool, you can
# manually force builds and inject changes, which may be useful for testing
# your buildmaster without actually commiting changes to your repository (or
# before you have a functioning 'sources' set up). The debug tool uses the
# same port number as the slaves do: 'slavePortnum'.

c['debugPassword'] = "helpme"

# if you set 'manhole', you can ssh into the buildmaster and get an
# interactive python shell, which may be useful for debugging buildbot
# internals. It is probably only useful for buildbot developers. You can 
also
# use an authorized_keys file, or plain telnet.
from buildbot import manhole
c['manhole'] = manhole.PasswordManhole("tcp:9999:interface=127.0.0.1",
                                       "admin", "password")

####### PROJECT IDENTITY

# the 'projectName' string will be used to describe the project that this
# buildbot is working on. For example, it is used as the title of the
# waterfall HTML page. The 'projectURL' string will be used to provide a 
link
# from buildbot HTML pages to your project's home page.

c['projectName'] = "BuildbotAware2"
c['projectURL'] = 
"http://wiki.wardrobe.irobot.com/mediawiki/index.php/Building_Aware_2"

# the 'buildbotURL' string should point to the location where the buildbot's
# internal web server (usually the html.Waterfall page) is visible. This
# typically uses the port number set in the Waterfall 'status' entry, but
# with an externally-visible host name which the buildbot cannot figure out
# without some help.

c['buildbotURL'] = "http://asimov:8010/"