You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Coverage for data_utils/utils/_multiprocessing.py : 95% Show keyboard shortcuts
85 statements 81 run 4 missing 0 excluded
But when I run test for whole tests directory the coverage for _multiprocessing.py and tests run after that dropped a lot -- compared to when being run in single file.
py.test --cov=data_utils --cov-report=html -vv -s
Coverage for data_utils/utils/_multiprocessing.py : 47% Show keyboard shortcuts
85 statements 40 run 45 missing 0 excluded
I am using Python 3.6.1 and pytest==3.4.2, pytest-cov==2.5.1,pytest-forked==0.2,pytest-mock==1.7.1 on ubuntu 16.04. I looked at #139 and I think this is not the same issue. The coverage is OK if run single test file but is too low if run the whole directory
The text was updated successfully, but these errors were encountered:
Sorry to reopen an old topic, but rather than being explained in the CHANGELOG, shouldn't the documentation be updated with the proposed fix? At the moment, the documentation is confusing as it still looks like multiprocessing is handled, even though it's not.
I am using multiprocessing.Process in some file. When I run test just for that file, seems the coverage data is OK.
And data:
But when I run test for whole tests directory the coverage for _multiprocessing.py and tests run after that dropped a lot -- compared to when being run in single file.
I am using Python 3.6.1 and pytest==3.4.2, pytest-cov==2.5.1,pytest-forked==0.2,pytest-mock==1.7.1 on ubuntu 16.04. I looked at #139 and I think this is not the same issue. The coverage is OK if run single test file but is too low if run the whole directory
The text was updated successfully, but these errors were encountered: