Hello Laurent, On 7 March 2012 20:56, Brack, Laurent P. <lpb...@dolby.com> wrote: > Somehow (and I don't know why), registering the plugin as 'timeout' instead > of 'pytest_timeout' was the cause of the problem, > so for it to work on my side, I had to do: > > config.pluginmanager.register(FaultHandlerPlugin(config), 'pytest_timeout')
Ah, I probably got something wrong with the setuptool entrypoints or something. I'll look into it, thanks for finding this! > I also played with the ability to use markers to override the default > timeout at the test level (here is an excerpt of > your code modified) [...] Thanks for this, I'll incorporate the timeout marker if you don't mind. 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
