summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLukas Slebodnik <lslebodn@redhat.com>2017-06-17 14:10:23 +0200
committerLukas Slebodnik <lslebodn@redhat.com>2017-06-19 13:59:53 +0200
commit223f4ff3cd9136414a8b593587f5742bf2c914cd (patch)
tree451a1edb680d13b8c9f445823a53b9a482e00f0a
parent05e579691b51ac2f81ab0c828ff6fe57bd86a8b6 (diff)
downloadsssd-223f4ff3cd9136414a8b593587f5742bf2c914cd.tar.gz
sssd-223f4ff3cd9136414a8b593587f5742bf2c914cd.tar.xz
sssd-223f4ff3cd9136414a8b593587f5742bf2c914cd.zip
CI: Do not use valgrind for dummy-child
There was a bug in valgrind < 3.13 which override some log files and therefore there was missing errors for shell wrappers generated by libtool for dummy-child. https://bugs.kde.org/show_bug.cgi?id=162848 We could add more suppressions for errors/leaks in bash to our suppression file but dummy child is built just for test purposes. Another possible solution would to avoid linking dummy-child with internal libraries; So libtool would not generate shell wrapper for dummy-child. But the simplest think is to ignore all errors for dummy-child. Reviewed-by: Fabiano FidĂȘncio <fidencio@redhat.com>
-rwxr-xr-xcontrib/ci/run2
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/ci/run b/contrib/ci/run
index a2f7f4f2d..fb72a33ac 100755
--- a/contrib/ci/run
+++ b/contrib/ci/run
@@ -214,7 +214,7 @@ function build_debug()
valgrind-condense 99 \
\"$valgrind_test_pattern\" -- \
--trace-children=yes \
- --trace-children-skip='*/bin/*,*/sbin/*' \
+ --trace-children-skip='*/bin/*,*/sbin/*,./dummy-child' \
--leak-check=full \
--gen-suppressions=all \
--suppressions=\"$CI_DIR/sssd.supp\" \