id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
95	foolscap.test.test_logging.IncidentGatherer.test_emit sometimes fails badly	Brian Warner		"{{{trial -r poll foolscap.test.test_logging.IncidentGatherer.test_emit}}} sometimes hangs for a long time (two minutes) and then fails with an error about ""maximum recursion depth exceeded"". I believe this is happening in the error-handling path, specifically in Twisted as it attempts to display whatever unhandled error was in the logs:
{{{
[ERROR]: foolscap.test.test_logging.IncidentGatherer.test_emit

Traceback (most recent call last):
  File ""/usr/lib/python2.5/site-packages/twisted/internet/defer.py"", line 289, in _continue
    self.unpause()
  File ""/usr/lib/python2.5/site-packages/twisted/internet/defer.py"", line 285, in unpause
    self._runCallbacks()
  File ""/usr/lib/python2.5/site-packages/twisted/internet/defer.py"", line 344, in _runCallbacks
    self.result = failure.Failure()
  File ""/usr/lib/python2.5/site-packages/twisted/python/failure.py"", line 265, in __init__
    parentCs = reflect.allYourBase(self.type)
  File ""/usr/lib/python2.5/site-packages/twisted/python/reflect.py"", line 542, in allYourBase
    accumulateBases(classObj, l, baseClass)
  File ""/usr/lib/python2.5/site-packages/twisted/python/reflect.py"", line 550, in accumulateBases
    accumulateBases(base, l, baseClass)
  File ""/usr/lib/python2.5/site-packages/twisted/python/reflect.py"", line 550, in accumulateBases
    accumulateBases(base, l, baseClass)
  File ""/usr/lib/python2.5/site-packages/twisted/python/reflect.py"", line 550, in accumulateBases
    accumulateBases(base, l, baseClass)
  File ""/usr/lib/python2.5/site-packages/twisted/python/reflect.py"", line 550, in accumulateBases
    accumulateBases(base, l, baseClass)
exceptions.RuntimeError: maximum recursion depth exceeded
}}}

I spent a couple of frustrated hours looking at this and wasn't able to figure it out. It seems like any error that occurs during certain tests will trigger this, which is really annoying as it doesn't make it easy to find out what the real error is.
"	defect	closed	major	0.3.1	unknown	0.3.0	fixed