[Buildbot-devel] Buildbot Fails Initial Tests on RHEL4

[Brian Warner]

"Roy S. Rapoport" <buildbot-devel at ols.inorganic.org> writes:

> I've just installed buildbot 0.7.4 (after installing TwistedCore,
> TwistedMail, and TwistedWeb (after installing ZopeInterface)) on an rhel4
> system.  Doing the startup tests to make sure my installation is sane gets
> me a bunch of errors (see below).  The CVS ones I'm not concerned about --
> the CVS environment is not set up for this user yet, and in either case,
> BuildBot's not going to be interacting with my VC system.  It looks like,
> fundamentally, there's something wrong in the mail area (it looks like
> pretty much all the mailparse tests failed), and there's something off with
> the shell stuff -- testShellSubdir is unhappy.  Any suggestions?

The unit tests use a number of non-.py helper files that are meant to get
installed into the buildbot/test/ directory along with the python code that
actually performs the unit tests. buildbot/test/subdir/emit.py is one of them
(used by the Shell tests), and buildbot/test/mail/msg[1234] are some more
(used by test_mailparse).

My guess is that these files didn't get installed quite right. Take a look in
/usr/lib/python2.3/site-packages/buildbot/test/mail/ and see if there's
anything there. It could be that they got installed but didn't get the right
permissions. I know that the code in setup.py that is supposed to install
them is a bit dubious, and it might depend upon some feature in distutils
that varies from one version of python to the next, or (less likely) upon
something that some distributions do differently than others.

Hm.

You know, now that you mention it, I just looked at a host where I installed
buildbot using the normal "setup.py install" command, and lo and behold, that
buildbot/test/mail/ directory isn't there. My bad. I guess the dubious goo in
setup.py serves to get those data files into the release tarball, but *not*
into the installation directory.

I'll see if I can fix that. In the meanwhile, just run the tests from the
source directory rather than on the installed form.

oops,
 -Brian