Hi Bruno / Obermann, As part of “pytest_sessionfinish” we are doing few major activities (collecting cluster logs, artifacts, screen shots & videos of testing and moving to central location), so if kill the pytest based on global timeout then i will lose all the important data which is required for analyzing.
if you have any other suggestions to hanldle global timeout for pytest, it will be great. Thanks -Shankar On Apr 20, 2016, at 7:12 PM, Bruno Oliveira <[email protected]> wrote: > > > On Wed, Apr 20, 2016 at 10:38 AM Obermann, Stephan > <[email protected]> wrote: > Just a thought, but if you want to kill the whole test run after 2h no matter > what the actual test results are - why not simply set a timeout in your test > automation system (the one that calls py.test). Most systems (Jenkins, > Electric Commander, etc.) provide this feature and it would spare you from > implementing your custom workflow logic on the "test runner" level. > > I second that, that's what we have in place here at work. > > Cheers, > Bruno.
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
