-
Notifications
You must be signed in to change notification settings - Fork 66
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.jl reporting lines surrounded by covered code as not covered #261
Comments
Was the line counted at all? Maybe that line was elided by the compiler in case it counts as neither a hit or a miss. That usually applieds to constant definitions etc. |
@vlandau Can you try running your test suite with inlining disabled, and see if that fixes the problem? I opened a pull request here: Circuitscape/Omniscape.jl#14 |
Thanks @DilumAluthge! Trying it now. |
It does seem that the coverage errors were significantly worse when the Note that this is all before trying with no inlining. I'll post the results here once that finishes running. |
In the second case (line 168 of |
Expected to be fixed by JuliaLang/julia#34254 |
🤦♂️ I thought I had a test that covered that line but I actually did not! Whoops. |
Appears to have been fixed (presumably by JuliaLang/julia#34254). Line count is still not perfect (some lines are skipped), but there are no longer any false negatives in the report (e.g. lines that were covered that are being reported as not covered). Closing this since it was about those false negatives. |
I'm noticing issues with a coverage report for my Julia package submitted to codecov showing lines of code as not covered that are surrounded by covered code. There is no control flow in this section of code -- basically, if lines n and n+2 were covered, then line n+1 must have also been covered, but the report is stating otherwise.
It could be something on codecov's end also, but wanted to post this here to make devs aware.
Here is the coverage report with an example highlighted for reference.
The text was updated successfully, but these errors were encountered: