-
-
Notifications
You must be signed in to change notification settings - Fork 437
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
Coverage 4.3 breaks "nosetest --with-coverage" #541
Comments
Do you have a .coveragerc file? Can you share your repo with me? |
Original comment by Diego Rodriguez-Losada (Bitbucket: drsada, GitHub: Unknown) Yes, the repo is: https://github.com/conan-io/conan And the builds that failed: https://travis-ci.org/conan-io/conan/builds/187080247 (fails the same in Windows with appveyor) I fixed my build forcing coverage==4.2. Thanks! |
@utek With coverage==4.2, do you find that the |
We're reverting that check to fix these problems. |
Original comment by Loic Dachary (Bitbucket: dachary, GitHub: dachary) For the record, the regression was introduced by https://bitbucket.org/ned/coveragepy/commits/4aced78ac2a1 incorrectly trying to implement https://bitbucket.org/ned/coveragepy/issues/265/when-using-source-include-is-silently |
Revert the check for conflicting --source and --include. Closes #541, re-opens #265 → <<cset d427811cbc79 (bb)>> |
Original comment by Diego Rodriguez-Losada (Bitbucket: drsada, GitHub: Unknown) Great, thanks! Will a patch coverage 4.3.1 be released with the fix? |
This fix has been released as part of version 4.3.1: https://pypi.python.org/pypi/coverage/4.3.1 |
Original comment by Diego Rodriguez-Losada (Bitbucket: drsada, GitHub: Unknown) 4.3.1 works fine again, thanks :) |
Issue #543 was marked as a duplicate of this issue. |
Originally reported by Diego Rodriguez-Losada (Bitbucket: drsada, GitHub: Unknown)
Just after upgrade, I get this
nosetests . --with-coverage
Traceback (most recent call last):
Downgrading to 4.2, everything fine again. Any suggestion? Thanks very much for your help
The text was updated successfully, but these errors were encountered: