systemd/test/units/TEST-07-PID1.sh

#!/usr/bin/env bash
# SPDX-License-Identifier: LGPL-2.1-or-later
set -eux
set -o pipefail

# shellcheck source=test/units/test-control.sh
. "$(dirname "$0")"/test-control.sh

# Issue: https://github.com/systemd/systemd/issues/2730
# See TEST-07-PID1/test.sh for the first "half" of the test
mountpoint /issue2730

run_subtests

touch /testok
systemctl --no-block exit 123
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`
tests: add spdx headers to scripts and Makefiles 2021-10-17 19:13:06 +03:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
test: use set -eux and set -o pipefail everywhere This should make the scripts more robust. 2021-04-09 20:39:41 +03:00			`set -eux`
			`set -o pipefail`
tests: add test for https://github.com/systemd/systemd/issues/1981 2015-11-23 20:56:45 +03:00
test: abstract the common test parts into a utility script Also, instead of bailing out on the first failed subtest, always run all subtests and print a summary at the end (with an appropriate exit code). 2023-05-10 22:12:01 +03:00			`# shellcheck source=test/units/test-control.sh`
			`. "$(dirname "$0")"/test-control.sh`

test: merge TEST-08-ISSUE-2730 into TEST-07-PID1 2023-05-10 14:07:26 +03:00			`# Issue: https://github.com/systemd/systemd/issues/2730`
			`# See TEST-07-PID1/test.sh for the first "half" of the test`
			`mountpoint /issue2730`

test: abstract the common test parts into a utility script Also, instead of bailing out on the first failed subtest, always run all subtests and print a summary at the end (with an appropriate exit code). 2023-05-10 22:12:01 +03:00			`run_subtests`
tests: add test for https://github.com/systemd/systemd/issues/1981 2015-11-23 20:56:45 +03:00
			`touch /testok`
TEST-07-PID1: Schedule exit on successful execution The test unit has RemainAfterExit=yes so let's schedule our own shutdown from the test itself once we finish running. 2024-05-04 23:19:22 +03:00			`systemctl --no-block exit 123`