]> git.ipfire.org Git - thirdparty/systemd.git/commit
test/test-functions: use binaries from $BUILD_DIR or installed system
authorDan Streetman <ddstreet@canonical.com>
Tue, 13 Aug 2019 11:52:57 +0000 (07:52 -0400)
committerYu Watanabe <watanabe.yu+github@gmail.com>
Sun, 25 Aug 2019 06:36:47 +0000 (15:36 +0900)
commit84c49ad197d78fb66a6f4d5ac540697ee36b46e1
tree64ae920fa26b83666a9fab9907f91d25a9eb1052
parente0eefa50a3b4dce561377ecf83081bfe53680555
test/test-functions: use binaries from $BUILD_DIR or installed system

In Ubuntu CI, we test binaries from the installed system, not from
$BUILD_DIR, so use the appropriate binary.  Most of the calls to the
binaries are part of checking/processing asan-built binaries, and so
did not apply to Ubuntu CI, except for generating noise in the stderr
log like:

objdump: '/tmp/autopkgtest.83yGoI/build.fHB/src/test/TEST-01-BASIC/systemd-journald': No such file

However this also applies to the call to systemd-nspawn, which the debian
upstream test wrapper was sed-adjusting to use the installed binary
instead of the binary in $BUILD_DIR.  This commit allows removing that
sed processing of the test-functions file during Ubuntu CI test.
test/test-functions