> On Mar 30, 2015, at 3:52 AM, Adi Roiban wrote:
>
> On 23 March 2015 at 15:29, Tristan Seligmann wrote:
>> On 23 March 2015 at 16:25, HawkOwl wrote:
>>> It's not really a bug -- it's just that the stderr isn't being captured
>>> like real Trial does. Twisted will reraise errors so they show
On 23 March 2015 at 15:29, Tristan Seligmann wrote:
> On 23 March 2015 at 16:25, HawkOwl wrote:
>> It's not really a bug -- it's just that the stderr isn't being captured like
>> real Trial does. Twisted will reraise errors so they show up in logs, but
>> will actually handle them (I think, any
On 23 March 2015 at 16:25, HawkOwl wrote:
> It's not really a bug -- it's just that the stderr isn't being captured like
> real Trial does. Twisted will reraise errors so they show up in logs, but
> will actually handle them (I think, anyway). The traceback formatting just
> says it's an unhand
> On 23 Mar 2015, at 22:05, Adi Roiban wrote:
>
> When running the pyhon3 tests I see many Unhandled Error
> ex:
> https://buildbot.twistedmatrix.com/builders/python-3.3-tests/builds/2736/steps/shell/logs/stdio
>
> This looks bad. Is this a bug in the test runner or a bug in the code?
>
> Than
