-
-
Notifications
You must be signed in to change notification settings - Fork 440
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
Non-existent filename triggers AttributeError. #153
Comments
Original comment by Brodie Rao (Bitbucket: brodie, GitHub: brodie) On a somewhat related note, I'm seeing this exact warning when running the Mercurial test suite with coverage 3.5.2. As far as I know, Mercurial's test runner doesn't try to run non-existent tests. I don't fully understand what's going on, but I've bisected the problem down to this commit: https://bitbucket.org/ned/coveragepy/changeset/edfe23dc34d3 Again, I have no idea what I'm doing, but this seemingly silly change gets rid of the problem:
|
Fixed in <<changeset 02e92889a5eb (bb)>>. |
Originally reported by Julian O (Bitbucket: oddthinking, GitHub: oddthinking)
Running coverage on a non-existent file gives a meaningful error message, and then signs off with an unexpected exception report.
I hope the following test case says it all:
Obviously, this isn't a big problem, but worth noting.
The text was updated successfully, but these errors were encountered: