Adjust tests to support tini-static

Valgrind does like statically-linked binaries due to false positives
coming from libc, which are ignord only if Valgrind can tell they're in
libc (which isn't the case when using static linking).
This commit is contained in:
Thomas Orozco 2015-06-26 21:33:16 +02:00
parent f2229f937e
commit 3577da19cf
1 changed files with 4 additions and 3 deletions

View File

@ -97,10 +97,11 @@ if __name__ == "__main__":
Command(functional_base_cmd + ["--", "zzzz"], fail_cmd).run(retcode=1)
Command(functional_base_cmd + ["-h"], fail_cmd).run()
# Valgrind test
Command(functional_base_cmd + ["--", "valgrind", "--leak-check=full", "--error-exitcode=1", entrypoint, "-v", "--", "ls"], fail_cmd).run()
# Valgrind test (we only run this on the dynamic version, because otherwise Valgrind may bring up plenty of errors that are
# actually from libc)
Command(functional_base_cmd + ["--", "valgrind", "--leak-check=full", "--error-exitcode=1", "/tini/dist/tini", "-v", "--", "ls"], fail_cmd).run()
# Install tests (sh -c is used for globbing and &&)
# Installation tests (sh -c is used for globbing and &&)
for image, pkg_manager, extension in [
["ubuntu:precise", "dpkg", "deb"],
["ubuntu:trusty", "dpkg", "deb"],