Skip to content
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

Running Valgrind on Tutorials #28

Open
pasetti opened this issue Dec 23, 2016 · 0 comments
Open

Running Valgrind on Tutorials #28

pasetti opened this issue Dec 23, 2016 · 0 comments
Assignees
Labels

Comments

@pasetti
Copy link
Contributor

pasetti commented Dec 23, 2016

I think that there is a minor inconsistency in the Release script for the FW Profile. At one point, the comment states: "Run the Demo Application and tutorials with Valgrind". However, Valgrind is only run on the demo application. Later in the script, where the headers are added to the test reports, the following commands are attempted:

sed -i -e "1i${H_L1}${H_ML6}${H_DATE}${H_CP}${H_VER}${H_L1}" ${OUT_LOG}/PR_Example1_Valgrind_Report.txt sed -i -e "1i${H_L1}${H_ML6}${H_DATE}${H_CP}${H_VER}${H_L1}" ${OUT_LOG}/RT_Example1_Valgrind_Report.txt sed -i -e "1i${H_L1}${H_ML3}${H_DATE}${H_CP}${H_VER}${H_L1}" ${OUT_LOG}/SM_Example1_Valgrind_Report.txt sed -i -e "1i${H_L1}${H_ML4}${H_DATE}${H_CP}${H_VER}${H_L1}" ${OUT_LOG}/SM_Example2_Valgrind_Report.txt sed -i -e "1i${H_L1}${H_ML5}${H_DATE}${H_CP}${H_VER}${H_L1}" ${OUT_LOG}/SM_Example3_Valgrind_Report.txt

These commands actually fail because the test reports do not exist. I assume that the intention was that these commands be commented out. If this is, please update the release script accordingly.

@pasetti pasetti added the bug label Dec 23, 2016
oppm pushed a commit that referenced this issue Jan 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants