-
Notifications
You must be signed in to change notification settings - Fork 68
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
Bug: Function declaration shown as missed although function body is hit #277
Comments
@vtjnash ^ |
Bump in case this got forgotten with GitHub's notification system? Also saw that this bug is produced for the coverage of... Coverage.jl! See, e.g., https://codecov.io/gh/JuliaCI/Coverage.jl/src/master/src/codecovio.jl#L36 |
@vtjnash ping? |
Those linked reports all look correct to me |
The line declaring the function looks green now, but still shows less hits than the function body, which cannot be correct, right? |
https://codecov.io/gh/JuliaCI/Coverage.jl/src/master/src/codecovio.jl looks fine right now: those @briochemc do you have a current example that can be viewed in public? |
This changed again since my last message, the "declaring" lines So yes, this looks fine now! 😃 If the Coverage.jl example is fine then I guess the issue has been resolved?
I'm not sure I understand what you mean? Both Coverage.jl and AIBECS.jl are public repositories and their coverages can be viewed "publicly", no? |
It's merging reports from multiple Julia versions, so that is correct. It's public, but Github might be blocking codecovio from displaying the source code for unauthenticated users, which may be resulting in confusion when not logged in to codecovio also (https://community.codecov.io/t/github-api-forbidden/1295/5) |
So I have codecov setup on AIBECS.jl and it oddly shows the lines declaring functions as missed. Here is a screenshot of such a case:
and here is a link to a similar codecov report with the same bug.
@vtjnash mentioned on slack that it may be due to a recent change in how line coverage was stored, and suggested I file a bug report, so here it is!
The text was updated successfully, but these errors were encountered: