-
Notifications
You must be signed in to change notification settings - Fork 36
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
Create unit_tests_Valgrind.yml #230
base: main
Are you sure you want to change the base?
Create unit_tests_Valgrind.yml #230
Conversation
praveenirumpanangadu
commented
Oct 30, 2024
- Adding valgrind support to the existing workflow to monitor the memory issues and performance
- This pull request was created as part of the following ticket (https://jira.rdkcentral.com/jira/browse/RDKBSUP-1687)
This pull request was created as part of the following ticket. https://jira.rdkcentral.com/jira/browse/RDKBSUP-1687
Internal ticket for tracking https://ccp.sys.comcast.net/browse/RDKCOM-5136 |
Addressing the review comments can you run the provider also with valgrind to get more better results
can you run the sessionmgr also with valgrind to get more better results
name: unit_tests_valgrind | ||
on: | ||
workflow_run: | ||
workflows: ["unit_tests"] |
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.
The workflow should run whenever a pull or push occurs to the branch.
export PREFIX=$PWD | ||
export LD_LIBRARY_PATH=$PREFIX/lib | ||
valgrind --leak-check=full --error-exitcode=1 ./bin/multiRbusOpenMethodProvider & | ||
valgrind --leak-check=full --error-exitcode=1 ./bin/multiRbusOpenMethodConsumer & |
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.
output need to be capture if any errors are detected