On Wed, Jun 26, 2002 at 05:22:03PM -0500, glyph CVS wrote:
> Note: With this checkin we (sean and I) discovered that the unit tests are
> starting to interfere with each other. Currently a full run of the tests will
> not complete, and will in fact hang and be unresponsive to signals. Running
> individual test cases by themselves work fine, but they're interfering with
> each other by doing reactor-y things ... we need each test case to
> instantiate/start/stop the reactor, etc. I will buy chocolate for whoever does
> this first.
Maybe reactors need a .reset() method to completely clear their internal
state? You could then modify runtests to do a reactor.reset() between
each testcase, or something similar. That way test cases that forget to
unregister old callLater calls, etc, won't pollute later tests.