[Buildbot-commits] [Buildbot] #2027: Unhandled error in Deferred (0.8.4p1)
Buildbot
nobody at buildbot.net
Thu Jun 30 05:04:55 UTC 2011
#2027: Unhandled error in Deferred (0.8.4p1)
--------------------+--------------------
Reporter: dberger | Owner:
Type: defect | Status: new
Priority: trivial | Milestone: 0.8.5
Version: 0.8.4p1 | Resolution:
Keywords: web |
--------------------+--------------------
Changes (by dustin):
* keywords: => web
* priority: major => trivial
* milestone: undecided => 0.8.5
Old description:
> I see this frequently in the buildmaster logs, though I haven't yet been
> able to correlate it with user-visible event(s)
>
> 2011-06-29 17:08:03-0700 [-] Unhandled error in Deferred:
> 2011-06-29 17:08:03-0700 [-] Unhandled Error
> Traceback (most recent call last):
> File
> "E:\build_master\external\Twisted-11.0.0\twisted\internet\defer.py", line
> 542, in _runCallbacks
> current.result = callback(current.result, *args, **kw)
> File
> "E:\build_master\external\Twisted-11.0.0\twisted\internet\defer.py", line
> 791, in _cbDeferred
> self.callback(self.resultList)
> File
> "E:\build_master\external\Twisted-11.0.0\twisted\internet\defer.py", line
> 361, in callback
> self._startRunCallbacks(result)
> File
> "E:\build_master\external\Twisted-11.0.0\twisted\internet\defer.py", line
> 455, in _startRunCallbacks
> self._runCallbacks()
> --- <exception caught here> ---
> File
> "E:\build_master\external\Twisted-11.0.0\twisted\internet\defer.py", line
> 542, in _runCallbacks
> current.result = callback(current.result, *args, **kw)
> File
> "E:\build_master\external\buildbot-0.8.4p1\buildbot\status\web\base.py",
> line 319, in ok
> request.finish()
> File
> "E:\build_master\external\Twisted-11.0.0\twisted\web\http.py", line 866,
> in finish
> "Request.finish called on a request after its connection was
> lost; "
> exceptions.RuntimeError: Request.finish called on a request after
> its connection was lost; use Request.notifyFinish to keep track of this.
New description:
I see this frequently in the buildmaster logs, though I haven't yet been
able to correlate it with user-visible event(s)
{{{
2011-06-29 17:08:03-0700 [-] Unhandled error in Deferred:
2011-06-29 17:08:03-0700 [-] Unhandled Error
Traceback (most recent call last):
File
"E:\build_master\external\Twisted-11.0.0\twisted\internet\defer.py", line
542, in _runCallbacks
current.result = callback(current.result, *args, **kw)
File
"E:\build_master\external\Twisted-11.0.0\twisted\internet\defer.py", line
791, in _cbDeferred
self.callback(self.resultList)
File
"E:\build_master\external\Twisted-11.0.0\twisted\internet\defer.py", line
361, in callback
self._startRunCallbacks(result)
File
"E:\build_master\external\Twisted-11.0.0\twisted\internet\defer.py", line
455, in _startRunCallbacks
self._runCallbacks()
--- <exception caught here> ---
File
"E:\build_master\external\Twisted-11.0.0\twisted\internet\defer.py", line
542, in _runCallbacks
current.result = callback(current.result, *args, **kw)
File
"E:\build_master\external\buildbot-0.8.4p1\buildbot\status\web\base.py",
line 319, in ok
request.finish()
File
"E:\build_master\external\Twisted-11.0.0\twisted\web\http.py", line 866,
in finish
"Request.finish called on a request after its connection was
lost; "
exceptions.RuntimeError: Request.finish called on a request after
its connection was lost; use Request.notifyFinish to keep track of this.
}}}
--
Comment:
This is common, and harmless. Basically what's happening is that the
browser is severing the connection before Buildbot has finished producing
data. You can reproduce it by clicking a button (e.g., force build)
repeatedly.
I'm not sure what the best way is to avoid the traceback.
--
Ticket URL: <http://trac.buildbot.net/ticket/2027#comment:1>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
More information about the Commits
mailing list