[Buildbot-devel] Locking stacktrace

Dobes Vandermeer dobesv at gmail.com
Fri Nov 4 23:57:17 UTC 2005

I seem to get a stacktrace like this sometimes:

2005/11/04 15:55 Pacific Standard Time [-] Traceback (most recent call last):
          File "Z:\Tools\PythonLibs\Python24\twisted\scripts\_twistw.py",
line 44, in runApp
            app.runReactorWithLogging(config, oldstdout, oldstderr)
          File "Z:\Tools\PythonLibs\Python24\twisted\application\app.py",
line 128, in runReactorWithLogging
          File "Z:\Tools\PythonLibs\Python24\twisted\internet\posixbase.py",
line 200, in run
          File "Z:\Tools\PythonLibs\Python24\twisted\internet\posixbase.py",
line 208, in mainLoop
        --- <exception caught here> ---
          File "Z:\Tools\PythonLibs\Python24\twisted\internet\base.py",
line 533, in runUntilCurrent
            call.func(*call.args, **call.kw)
          File "Z:\Tools\PythonLibs\buildbot\locks.py", line 43, in nowAvailable
            assert not self.owner

I think it may be caused by switching a builder from one slave to
another by reloading the configuration, when the builder has a
SlaveLock (although I don't think the SlaveLock is held, so its a bit
hard to debug).

Probably i could get more information if the status page showed which
lock(s) a builder was waiting for, on which slaves... hopefully
that'll be ready sometime soon? :-) :-)

More information about the devel mailing list