summaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2019-11-26 01:26:44 +0100
committerAllan McRae <allan@archlinux.org>2019-11-26 02:05:44 +0100
commit3073752bcd9718b243661dd727e8f8bc18035938 (patch)
tree93c96808f33533f7f1f9959951a5b0cd8d2532e0 /lib
parent49a8e90bc78c17600eb4903ba00be26341df9161 (diff)
downloadpacman-3073752bcd9718b243661dd727e8f8bc18035938.tar.gz
pacman-3073752bcd9718b243661dd727e8f8bc18035938.tar.xz
pactest: add environment option to run tests with valgrind
In autotools, if we wanted to run tests with valgrind, we used some Make magic which passed arguments to pactest.py, but that doesn't work in meson, because all arguments are encoded at configure time. Instead, let's short-circuit the build runner logic entirely, and teach pactest to default to running valgrind, when it detects an environment variable set independent of the build system. To run the tests with valgrind, we can now use: PACTEST_VALGRIND=1 meson test -C builddir/ or PACTEST_VALGRIND=1 make check It is also possible, but confusing/inconsistent, to use make check PY_LOG_FLAGS=--valgrind We *could* add a meson option -Dvalgrind=true, but that is annoying to reconfigure between test runs, and overall the consensus is it seems simpler to opt in each time we want to run valgrind, as was already the case. Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions