-
Notifications
You must be signed in to change notification settings - Fork 214
Use pytest_load_initial_conftests for startup #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I need this and am starting on it. will pull request |
doh. it's because it that was recently added, in pytest commit 083d8d0b. I'll do a slightly hacky thing for older versions of py.test. |
xdist integration is a royal pain. I think xdist is going to have to be modified to make this work, because I don't see any way to know we're in a slave process... |
Exactly the issue I have experienced: https://travis-ci.org/schlamar/pytest-cov/builds/23274310 |
I give up on xdist. I'm just going to make it revert to the old way of doing things if xdist is in use, and put a big comment in explaining what's going on and when it can be fixed. I carefully thumbed through the xdist code, and the only way to solve it would be soooo incredibly hacky (jam something into args). not going to go there. need to fix xdist to do that properly. |
See https://mail.python.org/pipermail/pytest-dev/2014-April/002494.html and https://bitbucket.org/memedough/pytest-cov/issue/12/doesnt-capture-coverage-on-imports-made
The text was updated successfully, but these errors were encountered: