Conversation
blueyed
force-pushed
the
coverage-source
branch
2 times, most recently
from
77887f0 to
615613d
Compare
Faster to install and will retry uploads on connection errors.
blueyed
force-pushed
the
coverage-source
branch
from
615613d to
2868b39
Compare
blueyed
changed the title
|
I'm investigating codecov problems with them. |
|
|
||
| [paths] | ||
| source = src/ | ||
| .tox/*/lib/python*/site-packages/ |
There was a problem hiding this comment.
This on Windows would be .tox\*e\Lib\site-packages. Can we add another entry here and coverage will try one and then the other?
There was a problem hiding this comment.
Yes, added .tox\*e\Lib\site-packages\.
This gets used with coverage report - so you could test it after e.g. tox -e py36-coverage -- testing/deprecated_test.py.
This should increase coverage for subprocesses, where previously `source` paths were used only from the config file, but not the initial `--source` argument.
blueyed
force-pushed
the
coverage-source
branch
from
2868b39 to
28c9cc7
Compare
Codecov Report
@@ Coverage Diff @@
## master #3990 +/- ##
==========================================
+ Coverage 94.48% 94.53% +0.04%
==========================================
Files 107 108 +1
Lines 23663 23686 +23
Branches 2349 2350 +1
==========================================
+ Hits 22358 22391 +33
+ Misses 994 988 -6
+ Partials 311 307 -4
Continue to review full report at Codecov.
|
3 participants
This should increase coverage for subprocesses, where
sourceis usedonly from the config file, but not the initial
--sourceargument.