-
Notifications
You must be signed in to change notification settings - Fork 6.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
rename zassert functions #21783
Labels
Enhancement
Changes/Updates/Additions to existing features
Comments
I am not familiar with Coverity so do not know if this is possible, but IMHO we should instead try to configure Coverity to not generate these false positives. It sounds wrong to change our code just to satisfy some weird rule in a tool. |
agree with @jukkar |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Coverity thinks any function with the word "assert" in its name is a conditionally compiled expression, and generates false positives about side effects.
To avoid this hassle, rename the zassert... family of APIs used in our test cases to something which doesn't have "assert" in the same. zcheck perhaps?
The existing APIs should be marked with __deprecated and just call the new APIs. All test cases should be converted.
The text was updated successfully, but these errors were encountered: