systemd-stable/test/units/testsuite-37.sh

#!/usr/bin/env bash
# SPDX-License-Identifier: LGPL-2.1-or-later
# -*- mode: shell-script; indent-tabs-mode: nil; sh-basic-offset: 4; -*-
# ex: ts=8 sw=4 sts=4 et filetype=sh
set -eux
set -o pipefail

systemd-mount -p RuntimeDirectory=hoge -p RuntimeDirectoryPreserve=yes -t tmpfs tmpfs /tmp/aaa

touch /run/hoge/foo
touch /tmp/aaa/bbb

systemctl restart tmp-aaa.mount

test -e /run/hoge/foo
test ! -e /tmp/aaa/bbb

echo OK >/testok

exit 0
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`
tests: add spdx headers to scripts and Makefiles 2021-10-17 18:13:06 +02:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
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`
test: use set -eux and set -o pipefail everywhere This should make the scripts more robust. 2021-04-09 19:39:41 +02:00			`set -eux`
test: add tests for RuntimeDirectoryPreserve=yes 2019-08-23 00:22:54 +09:00			`set -o pipefail`

			`systemd-mount -p RuntimeDirectory=hoge -p RuntimeDirectoryPreserve=yes -t tmpfs tmpfs /tmp/aaa`

			`touch /run/hoge/foo`
			`touch /tmp/aaa/bbb`

			`systemctl restart tmp-aaa.mount`

			`test -e /run/hoge/foo`
tests: make inverted tests actually count "! test ..." does not cause the script to fail, even with set -e. IIUC, bash treats this command as part of an expression line, as it would if 'test ... && ...' was used. Failing expression lines do not terminate the script. This fixes the obvious cases by changing '! test' → 'test !'. Then the inversion happens internally in test and bash will propagate the failure. 2021-04-07 23:24:25 +02:00			`test ! -e /tmp/aaa/bbb`
test: add tests for RuntimeDirectoryPreserve=yes 2019-08-23 00:22:54 +09:00
TEST-*: use spacing before redirection operator, but not after << EOF → <<EOF > foo < bar → >foo <bar 2021-04-08 00:09:55 +02:00			`echo OK >/testok`
test: add tests for RuntimeDirectoryPreserve=yes 2019-08-23 00:22:54 +09:00
			`exit 0`