systemd/test/TEST-10-ISSUE-2467/test.sh

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

TEST_DESCRIPTION="https://github.com/systemd/systemd/issues/2467"

# 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 12:35:06 +03:00			`#!/usr/bin/env bash`
test: Run qemu/nspawn tests with "set -e" This catches errors like "ninja not found", missing programs etc. early, instead of silently ignoring them and trying to boot a broken VM. In install_config_files(), allow some distro specific files to be absent (such as /etc/sysconfig/init). 2017-08-07 22:09:21 +03:00			`set -e`
test: make the test entrypoint scripts shellcheck-compliant 2021-04-19 14:01:59 +03:00
tests: add test for https://github.com/systemd/systemd/issues/2467 (#3168) 2016-05-02 11:57:19 +03:00			`TEST_DESCRIPTION="https://github.com/systemd/systemd/issues/2467"`

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"`
tests: add test for https://github.com/systemd/systemd/issues/2467 (#3168) 2016-05-02 11:57:19 +03: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 20:20:18 +03:00			`do_test "$@"`