-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Fix issues reported by Coverity Scan #192
Comments
Another issue with Coverity Scan: https://communities.coverity.com/thread/3462 |
Nothing to do here until Coverity Scan is fixed. |
Now that Coverity Scan issue is fixed, remaining issues can be addressed. |
Two bogus Coverity warnings should be fixed in e81c0ae. |
As of e104ba5 we are down to 3 issues. |
Have to wait till 25 October because of the submission limit. |
And reported a bug in Coverity Scan in https://communities.coverity.com/thread/3484. |
As of 2d727e7 all warnings fixed or suppressed (if false positive). |
Coverity Scan report: https://scan.coverity.com/projects/5671
The issues are not critical and only affect tests. Some of them are in Google Mock, but a bug in Coverity Scan prevents adding the latter as a component and ignoring its issues: https://communities.coverity.com/message/7086#7086.
The text was updated successfully, but these errors were encountered: