-
Notifications
You must be signed in to change notification settings - Fork 0
Add Valgrind Targets to Unit Tests [DEVINFRA-550] #102
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
Conversation
silverjam
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM-- please clean up PR title before merge (remove username and add Jira tag)
jbangelo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Exactly what I was hoping for. Thanks for the quick turn around on this @isaactorz !
d9da73a to
a9bdecb
Compare
Often in Starling when a unit test is added with swift_add_test, a corresponding valgrind-membeck target is added. For convenience, an optional parameter, VALGRIND_MEMCHECK, has been added to swift_add_test to automatically create a valgrind target from the unit test definition.
a9bdecb to
31d066a
Compare
|
Kudos, SonarCloud Quality Gate passed! |








Jira
Added a
VALGRIND_MEMCHECKoption toswift_add_testfor unit tests. This will callswift_valgrind_memcheckwith a default set of parameters. Respects the${PROJECT_NAME}_ENABLE_PROFILINGoption.