security: Fix valgrind output file

It was generated into iotivity/ut instead of .memcheck file.

Bug: https://jira.iotivity.org/browse/IOT-2599
Change-Id: Ib96a6378513df77e7415378cd37a864fa0cbebb9
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/22021
Reviewed-by: Alex Kelley <alexke@microsoft.com>
Reviewed-by: Pawel Winogrodzki <pawelwi@microsoft.com>
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Randeep Singh <randeep.s@samsung.com>

diff --git a/resource/csdk/security/unittest/SConscript b/resource/csdk/security/unittest/SConscript
index 52ba3d2..6c81321 100644 (file)
--- a/resource/csdk/security/unittest/SConscript
+++ b/resource/csdk/security/unittest/SConscript
@@ -152,4 +152,6 @@ if srmtest_env.get('TEST') == '1':
             os.makedirs(result_dir)
         srmtest_env.AppendENVPath('GTEST_OUTPUT', ['xml:' + result_dir])
         srmtest_env.AppendENVPath('LD_LIBRARY_PATH', [out_dir])
-        run_test(srmtest_env, 'ut', 'resource/csdk/security/unittest/unittest')
+        run_test(srmtest_env,
+                 'resource_csdk_security_unittest.memcheck',
+                 'resource/csdk/security/unittest/unittest')