systemd-stable/test/TEST-22-TMPFILES/test.sh

#!/usr/bin/env bash
set -e

TEST_DESCRIPTION="Tmpfiles related tests"
TEST_NO_QEMU=1

# shellcheck source=test/test-functions
. "${TEST_BASE_DIR:?}/test-functions"

test_append_files() {
    if [[ "${IS_BUILT_WITH_ASAN:=}" == "yes" ]]; then
        if [[ -z "${initdir:=}" ]]; then
            echo >&2 "\$initdir is not defined, can't continue"
            exit 1
        fi

        sed -i "s/systemd//g" "$initdir/etc/nsswitch.conf"
    fi
}

do_test "$@"
treewide: more portable bash shebangs As in 2a5fcfae024ffc370bb780572279f45a1da3f946 and in 3e67e5c9928f8b1e1c5a63def88d53ed1fed12eb using /usr/bin/env allows bash to be looked up in PATH rather than being hard-coded. As with the previous changes the same arguments apply - distributions have scripts to rewrite shebangs on installation and they know what locations to rely on. - For tests/compilation we should rather rely on the user to have setup there PATH correctly. In particular this makes testing from git easier on NixOS where do not provide /bin/bash to improve compose-ability. 2020-03-04 12:35:06 +03:00			`#!/usr/bin/env bash`
test: add tests for systemd-tmpfiles 2018-03-05 14:32:18 +03:00			`set -e`
test: make the test entrypoint scripts shellcheck-compliant 2021-04-19 14:01:59 +03:00
test: add tests for systemd-tmpfiles 2018-03-05 14:32:18 +03:00			`TEST_DESCRIPTION="Tmpfiles related tests"`
			`TEST_NO_QEMU=1`
test: make the test entrypoint scripts shellcheck-compliant 2021-04-19 14:01:59 +03:00
			`# shellcheck source=test/test-functions`
			`. "${TEST_BASE_DIR:?}/test-functions"`
test: add tests for systemd-tmpfiles 2018-03-05 14:32:18 +03:00
test: disable nss-systemd for TEST-22 under ASan When running TEST-22 under ASan, there's a chain of events which causes `stat` to output an extraneous ASan error message, causing following fail: ``` + test -d /tmp/d/1 ++ stat -c %U:%G:%a /tmp/d/1 ==82==ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD. + test = daemon:daemon:755 .//usr/lib/systemd/tests/testdata/units/testsuite-22.02.sh: line 24: test: =: unary operator expected ``` This is caused by `stat` calling nss which in Arch's configuration calls the nss-systemd module, that pulls in libasan which causes the $LD_PRELOAD error message, since `stat` is an uninstrumented binary. The $LD_PRELOAD variable is explicitly unset for all testsuite-* services since it causes various issues when calling uninstrumented libraries, so setting it globally is not an option. Another option would be to set $LD_PRELOAD for each `stat` call, but that would unnecessarily clutter the test code. 2021-03-10 00:20:39 +03:00			`test_append_files() {`
test: make the test entrypoint scripts shellcheck-compliant 2021-04-19 14:01:59 +03:00			`if [[ "${IS_BUILT_WITH_ASAN:=}" == "yes" ]]; then`
			`if [[ -z "${initdir:=}" ]]; then`
test: disable nss-systemd for TEST-22 under ASan When running TEST-22 under ASan, there's a chain of events which causes `stat` to output an extraneous ASan error message, causing following fail: ``` + test -d /tmp/d/1 ++ stat -c %U:%G:%a /tmp/d/1 ==82==ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD. + test = daemon:daemon:755 .//usr/lib/systemd/tests/testdata/units/testsuite-22.02.sh: line 24: test: =: unary operator expected ``` This is caused by `stat` calling nss which in Arch's configuration calls the nss-systemd module, that pulls in libasan which causes the $LD_PRELOAD error message, since `stat` is an uninstrumented binary. The $LD_PRELOAD variable is explicitly unset for all testsuite-* services since it causes various issues when calling uninstrumented libraries, so setting it globally is not an option. Another option would be to set $LD_PRELOAD for each `stat` call, but that would unnecessarily clutter the test code. 2021-03-10 00:20:39 +03:00			`echo >&2 "\$initdir is not defined, can't continue"`
			`exit 1`
			`fi`

			`sed -i "s/systemd//g" "$initdir/etc/nsswitch.conf"`
			`fi`
			`}`

test: "detect" the test number automagically Specifying the test number manually is tedious and prone to errors (as recently proven). Since we have all the necessary data to work out the test number, let's do it automagically. 2021-04-26 20:20:18 +03:00			`do_test "$@"`