On Mon, 25 Sep 2006 18:06:50 +0200, Michele Petrazzo <michele.petrazzo@unipex.it> wrote:
glyph@divmod.com wrote:
You have lots of other options.
1. Continue using the wxreactor code by copying it into your application. We could even provide a separate page with "unmaintained reactors" for download.
For me, if you don't find someone that help you to maintain the wx reactor, this are a good solution, since there are a lot of person, like me, that use the (fantastic) twisted library and wx like GUI.
2. Help fix the problem. This is really what I'd prefer. You don't have to have all the appropriate knowledge right now, just sufficient interest and energy to commit to *caring* that the buildbot is red in the future, and trying to fix it.
Just for see if I can help, I tried the "trial --reactor threadedselect twisted", but after some (10 min) work, trial eat all my ram! and I must close it with e "kill -9". Are there another method for execute trial?
As a comparison, have you run trial with the default reactor? If this fails the same way, your machine have an odd configuration which is fouling up the tests, or it may simply not have enough ram to run the full test suite. On the other hand, if this runs successfully, then what you are seeing is basically one aspect of the current problem with threadedselect reactor :) Jean-Paul