-
Notifications
You must be signed in to change notification settings - Fork 31
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
The process is hanging when using .coveragerc with include or source setting #136
Comments
As my library a python dependency, I removed coverage from Sublime Text to a exclusive job on the |
I have no idea what you are trying to demonstrate.... |
Using the include setting for coverage blocks the unit tests from completing. |
If I understand correctly, this issue is also caused by:
Where coverage dependency was being deleted. |
I actually, it cannot be otherwise the unit tests would not start running and would fail with the same error as the other issue. I think it could be because the coverage dependency is out of date, because when running it outside Sublime Text and installing the coverage dependency with |
This is a build result without specifying the
include
setting with.coveragerc
:This is a build where I specified the
include
setting:Took me several hours until nail it down to this. I even modified the
test_coverage.py
adding a setting for theinclude
directory:And it still hanging on the same place, whether the setting is passed by
unittesting.json
or by.coveragerc
. This only happens for the Sublime Text build. Build for other python versions work fine:After experimenting, I notice it always hang on the penultimate test. For example, If there are 10 tests it will hang on the 9th test. If I remove 1 test, then it will hang on the 8th.
I even had modified the UnitTesting AppVeyor script adding a lot of prints, but it shows there is nothing to do with the powershell:
Apart this issue, I am trying to set the
include
setting becausecodecov
is not finding my source code underall/debug_tools
directory:Codecov thinks that the only source on the repository is the file
setup.py
.The text was updated successfully, but these errors were encountered: