We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Originally reported by shauncutts (Bitbucket: shauncutts, GitHub: Unknown)
say we have test1.py such as:
#!python # from peak.util.addons import AddOn def foo(): print "bar" foo()
Now, if I run coverage on this
#!shell > coverage -e -x test.py > coverage -r test.py Name Stmts Exec Cover --------------------------- test 3 3 100%
it works fine. However, with the first "include" line uncommented, it breaks:
#!shell > coverage -e -x test.py > coverage -r test.py Name Stmts Exec Cover --------------------------- test 4 1 25%
If coverage is being run by nosetests, then it reports 0 coverage for all modules after the first one with an "addons" include.
-- Shaun
PS -- Great tool, by the way. I'd try to do more diagnosis if I weren't in the middle of a coding grind.
The text was updated successfully, but these errors were encountered:
The fix for this is in <<changeset a480f40d1fa4 (bb)>>, but you have to enable it with the --timid flag, or setenv COVERAGE_OPTIONS="--timid"
Sorry, something went wrong.
Removing version: 3.0.1 (automated comment)
Ensured that the TaskGroup._active attribute is set to False at the end
c8a0065
Closes nedbat#13.
No branches or pull requests
Originally reported by shauncutts (Bitbucket: shauncutts, GitHub: Unknown)
say we have test1.py such as:
Now, if I run coverage on this
it works fine. However, with the first "include" line uncommented, it breaks:
If coverage is being run by nosetests, then it reports 0 coverage for all modules after the first one with an "addons" include.
-- Shaun
PS -- Great tool, by the way. I'd try to do more diagnosis if I weren't in the middle of a coding grind.
The text was updated successfully, but these errors were encountered: