[Buildbot-devel] Unable to utilize 'manhole' module in buildbot

[Kenneth Lareau]

Well, it looks like this problem is going to be a real pain, it seems... see below...

On Tue, 06 Feb 2007 21:00:28 -0800 Brian Warner <warner-buildbot at lothar.com> wrote:

> Kenneth Lareau <elessar at numenor.org> writes:
> 
> > I've been having a few issues keeping everything running smoothly.  I do
> > suspect this has something to do with the fact that we have 188 builders
> 
> Wow! I can't imagine what you've done to the Waterfall display to make that
> usable :).
> 
> > Software: buildbot 0.7.4
> >           Python 2.4.3
> >           pycrypto 2.0.1
> >           Twisted Conch 0.8.0
> >
> >   From buildbot import manhole
> >   c['manhole'] = manhole.AuthorizedKeysManhole(6561, "~/.ssh/authorized_keys")
> >           File "/eng/os/rhel-3/i386/python/lib/python2.4/site-packages/twisted/conch/insults/insults.py", line 77, in ?
> >             class ITerminalTransport(iinternet.ITransport):
> >           File "/eng/os/rhel-3/i386/python/lib/python2.4/site-packages/twisted/python/components.py", line 168, in __init__
> >             attrs[k] = interface.fromFunction(v, name, name=k, imlevel=1)
> >           File "/eng/os/rhel-3/i386/python/lib/python2.4/site-packages/zope/interface/interface.py", line 907, in fromFunction
> >             method.varargs = names[argno]
> >         exceptions.IndexError: tuple index out of range
> 
> That exception makes me think that it is a compatibility issue between the
> installed versions of Twisted and zope.interface . If I had to guess, I'd say
> your zope.interface is too old.
> 
> Check the README on that Twisted Conch package and see what version of
> zope.interface they recommend. The dependency graph might be Twisted-Conch ->
> Twisted-Core -> zope.interface . It's also possible that the issue is the
> other way round: that you have a new zope.interface but an old twisted.conch
> .
> 
> Let me know if that doesn't do it and we can investigate further.

The README says nothing about which zope.interface to use.  I was unable to
tell what version we were using, though I was pretty sure it was at least 3.0.1,
but when I upgraded TwistedCore to 2.5.0 and tried to restart buildbot, I got
the following failure:

          File "/eng/os/rhel-3/i386/python/lib/python2.4/site-packages/twisted/application/app.py", line 218, in getApplication
            application = service.loadApplication(filename, style, passphrase)
          File "/eng/os/rhel-3/i386/python/lib/python2.4/site-packages/twisted/application/service.py", line 341, in loadApplication
            application = sob.loadValueFromFile(filename, 'application', passphrase)
          File "/eng/os/rhel-3/i386/python/lib/python2.4/site-packages/twisted/persisted/sob.py", line 215, in loadValueFromFile
            exec fileObj in d, d 
          File "buildbot.tac", line 3, in ?
            from buildbot.master import BuildMaster
          File "/eng/os/rhel-3/i386/python/lib/python2.4/site-packages/buildbot/master.py", line 28, in ?
            from buildbot.changes.changes import Change, ChangeMaster
          File "/eng/os/rhel-3/i386/python/lib/python2.4/site-packages/buildbot/changes/changes.py", line 15, in ?
            from twisted.web import html
          File "/eng/os/rhel-3/i386/python/lib/python2.4/site-packages/twisted/web/html.py", line 11, in ?
            from twisted.web import resource
          File "/eng/os/rhel-3/i386/python/lib/python2.4/site-packages/twisted/web/resource.py", line 15, in ?
            class IResource(components.Interface):
        exceptions.AttributeError: 'module' object has no attribute 'Interface'

I thankfully had saved a copy of the site-packages directory before I did the new install,
and reverted the changes.  At this point I'm getting the feeling I'll need to do a fully
clean install of everything from the ground-up. *sigh*

The whole reason for wanting the 'manhole' module enabled in the first place was because
we have a set of dependant builders that aren't being run any more, and we can't track
down any change that would've caused this problem.  In fact, between the last successful
run of the builders and the first night where they didn't run, there were NO changes to
any of the configuration files, so I'm at a loss as to what happened.

Any suggestions to be made here are gratefully welcome!

Ken


-- 
Ken Lareau
elessar at numenor.org