This problem is resolved with r14989.<br><br>
<div><span class="gmail_quote">On 10/29/05, <b class="gmail_sendername">Andrew Bennetts</b> <<a href="mailto:andrew-twisted@puzzling.org">andrew-twisted@puzzling.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Fri, Oct 28, 2005 at 11:26:22PM -0400, Jean-Paul Calderone wrote:<br>> On Fri, 28 Oct 2005 10:38:02 -0600, Justin Johnson
<br>> <<a href="mailto:justinj@wolfwood.twistedmatrix.com">justinj@wolfwood.twistedmatrix.com</a>> wrote:<br>[...]<br>> >Log:<br>> >Impelement spawnProcess for IOCP reactor. Resolves issue1008.<br>> >
<br>><br>> While I am excited this feature is so close, it seems like it isn't quite<br>> there yet. Buildbot is now reporting only 442 tests run by the IOCP<br>> builder on Win32, and a really nasty looking traceback afterwards.
<br>><br>> Could we revert this merge?<br><br>The bug you notice existed before that merge too. Jonathan helped me<br>diagnose it: see <a href="http://twistedmatrix.com/bugs/issue1294">http://twistedmatrix.com/bugs/issue1294
</a>. It appears trial<br>is calling reactor.iterate(0) during cleanup, and not expecting that it<br>could raise an exception. Making iocp's doIteration swallow and log that<br>error, like the other reactors do, will probably fix this. Making trial
<br>deal with that error better (as apparently is not too hard to do with one of<br>the trial branches) would also fix it.<br><br>-Andrew.<br><br><br>_______________________________________________<br>Twisted-Python mailing list
<br><a href="mailto:Twisted-Python@twistedmatrix.com">Twisted-Python@twistedmatrix.com</a><br><a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
</a><br></blockquote></div><br>