The teardown of the py.test 2.3 fixtures is executed outside of the timeout-managed code. Especially session-scoped fixtures appear to be torn down after the session itself is torn down. The result is that a hang in the teardown does not get caught by pytest-timeout
pytest-timeout-bot
commented
10 years ago
Original report by Floris Bruynooghe (Bitbucket: flub, GitHub: flub).
The teardown of the py.test 2.3 fixtures is executed outside of the timeout-managed code. Especially session-scoped fixtures appear to be torn down after the session itself is torn down. The result is that a hang in the teardown does not get caught by pytest-timeout