-
Notifications
You must be signed in to change notification settings - Fork 283
Make gcovr return -1 #716
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
Comments
@latk Here I need your advice. I'm not sure but I think a error would be better here maybe with an option to turn into warning. If the configuration is correct, this error should never ocure. |
I would say it is an error for sure! |
Gcovr has always ignored gcov errors (with this warning). When no gcov invocation works for a given input file, I'd agree that a hard error should be raised, instead of skipping that file. Especially on large projects, there can be value in continuing with partial data. But especially in CI settings, warnings would go entirely unnoticed. Thus, I think errors that can be easily downgraded to warnings are sensible, just like we're treating unrecognized syntax in gcov files. |
@MartinDelille Can you check the behavior with the branch in the linked PR? |
I'm using gcovr via pip so I wonder how to use a development branch since I'm not a python developer. I cloned the repo and checked out the branch so now what is the command line equivalent to running the local version of gcovr ? |
Run |
Here is my output:
Looks good to me! |
I wondered if it is possible to return an error code when such warning occurs:
It currently fails silently.
The text was updated successfully, but these errors were encountered: