-
Notifications
You must be signed in to change notification settings - Fork 28
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
Fine-tune coverage execution #77
Comments
Have you tried any of those? It seems to me that it would be useful to have tests around these issues before fixing them. Can you write the tests that prove the issue? Thanks!!! |
Makes sense. ☺ Will try to test this shortly. |
coverage + GEventConfirmed. On coverage’s gevent issue, Ned Batchelder said:
Here is coverage as pyvows currently stands:
Next, I uninstalled The difference is not huge, but it’s there:
|
Problem
Part I
The documentation for coverage states that GEvent can confuse coverage’s results:
Part II
Should we be using
--timid
?Source: http://nedbatchelder.com/code/coverage/cmd.html#cmd-execution
Part III
Should we be using
--parallel-mode
?Source: http://nedbatchelder.com/code/coverage/cmd.html#cmd-execution
Summary
--timid
--parallel-mode
The text was updated successfully, but these errors were encountered: