From 0a0d4c6d0923e5bb4091d536f82014e0e3e6713f Mon Sep 17 00:00:00 2001
From: Martin Hierholzer <martin.hierholzer@desy.de>
Date: Fri, 23 Nov 2018 16:52:59 +0100
Subject: [PATCH] do not run valgrind with trace children, as it leads to
strange errors. if needed, we should add this as an option
---
vars/helper.groovy | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/vars/helper.groovy b/vars/helper.groovy
index 3ba8f64..6d52cbd 100644
--- a/vars/helper.groovy
+++ b/vars/helper.groovy
@@ -247,8 +247,8 @@ def doValgrind(String label, String buildType) {
for test in \${EXECLIST} ; do
testname=`basename \${test}`
if [ -z "`echo " \${valgrindExcludes} " | grep " \${testname} "`" ]; then
- sudo -u msk_jenkins valgrind --gen-suppressions=all --suppressions=/common/valgrind.suppressions/ChimeraTK.supp --trace-children=yes --tool=memcheck --leak-check=full --undef-value-errors=yes --xml=yes --xml-file=/scratch/build-${parentJob}/valgrind.\${testname}.memcheck.valgrind \${test}
- # sudo -u msk_jenkins valgrind --gen-suppressions=all --suppressions=/common/valgrind.suppressions/ChimeraTK.sup --trace-children=yes --tool=helgrind --xml=yes --xml-file=/scratch/build-${parentJob}/valgrind.\${testname}.helgrind.valgrind \${test}
+ sudo -u msk_jenkins valgrind --gen-suppressions=all --suppressions=/common/valgrind.suppressions/ChimeraTK.supp --tool=memcheck --leak-check=full --undef-value-errors=yes --xml=yes --xml-file=/scratch/build-${parentJob}/valgrind.\${testname}.memcheck.valgrind \${test}
+ # sudo -u msk_jenkins valgrind --gen-suppressions=all --suppressions=/common/valgrind.suppressions/ChimeraTK.sup --tool=helgrind --xml=yes --xml-file=/scratch/build-${parentJob}/valgrind.\${testname}.helgrind.valgrind \${test}
fi
done
cd /scratch/build-${parentJob}
--
GitLab