systemd-stable/test/TEST-37-RUNTIMEDIRECTORYPRESERVE/test.sh

#!/usr/bin/env bash
# -*- mode: shell-script; indent-tabs-mode: nil; sh-basic-offset: 4; -*-
# ex: ts=8 sw=4 sts=4 et filetype=sh
set -e

TEST_DESCRIPTION="test RuntimeDirectoryPreserve=yes"

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

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 09:35:06 +00:00			`#!/usr/bin/env bash`
test: add tests for RuntimeDirectoryPreserve=yes 2019-08-23 00:22:54 +09:00			`# -- mode: shell-script; indent-tabs-mode: nil; sh-basic-offset: 4; --`
			`# ex: ts=8 sw=4 sts=4 et filetype=sh`
			`set -e`
test: make the test entrypoint scripts shellcheck-compliant 2021-04-19 13:01:59 +02:00
test: add tests for RuntimeDirectoryPreserve=yes 2019-08-23 00:22:54 +09:00			`TEST_DESCRIPTION="test RuntimeDirectoryPreserve=yes"`
test: make the test entrypoint scripts shellcheck-compliant 2021-04-19 13:01:59 +02:00
			`# shellcheck source=test/test-functions`
			`. "${TEST_BASE_DIR:?}/test-functions"`
test: add tests for RuntimeDirectoryPreserve=yes 2019-08-23 00:22:54 +09:00
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 19:20:18 +02:00			`do_test "$@"`