Hi, in addition something for eventlet/gevent based timeout objects as well as a ini option to choose the timeout method between signal/thread, gevent, eventlet could be nice
best, ronny On 03/07/2012 10:55 PM, holger krekel wrote: > Hi Floris, > > thanks for the plugin! > > looking at version 0.1 i wonder why you didn't go with always activating > the plugin so not requiring any pytest_plugins setting. The default > could be "no timeout" or None which could be modified with: > > [pytest] > timeout = 2.3 # secs > > or with a marker. Not using some implicit magic number is anyway a good > idea i think. > > best, > holger > > On Sun, Feb 26, 2012 at 23:19 +0000, Floris Bruynooghe wrote: >> Hi all, >> >> This is to announce the first release of pytest-timeout, a plugin >> which will interrupt long running (i.e. blocking) tests. This is >> particularly useful when running the tests on a CI host. When a test >> is interrupted the stacks of all threads are dumped to stderr, which >> helps you to locate the reason for the blocking. If the system >> supports SIGALRM then the test itself is interrupted using >> pytest.fail() and other tests continue to run, otherwise the stack(s) >> are dumped to stderr and the process exists immediately. >> >> The plugin is available from the cheeseshop: >> http://pypi.python.org/pypi/pytest-timeout and the code lives at >> bitbucket: https://bitbucket.org/flub/pytest-timeout/. Feel free to >> provide any feedback or report issues. >> >> Regards, >> Floris >> >> -- >> Debian GNU/Linux -- The Power of Freedom >> www.debian.org | www.gnu.org | www.kernel.org >> _______________________________________________ _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
