ff12a7954c
As in2a5fcfae02and in3e67e5c992using /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.
38 lines
697 B
Bash
Executable file
38 lines
697 B
Bash
Executable file
#!/usr/bin/env bash
|
|
set -e
|
|
TEST_DESCRIPTION="test systemd-repart"
|
|
|
|
. $TEST_BASE_DIR/test-functions
|
|
|
|
test_setup() {
|
|
create_empty_image_rootdir
|
|
|
|
(
|
|
LOG_LEVEL=5
|
|
eval $(udevadm info --export --query=env --name=${LOOPDEV}p2)
|
|
|
|
setup_basic_environment
|
|
|
|
mask_supporting_services
|
|
dracut_install truncate sfdisk grep
|
|
|
|
# setup the testsuite service
|
|
cat >$initdir/etc/systemd/system/testsuite.service <<EOF
|
|
[Unit]
|
|
Description=Testsuite service
|
|
Before=getty-pre.target
|
|
Wants=getty-pre.target
|
|
|
|
[Service]
|
|
ExecStart=/testsuite.sh
|
|
Type=oneshot
|
|
EOF
|
|
cp testsuite.sh $initdir/
|
|
|
|
setup_testsuite
|
|
)
|
|
setup_nspawn_root
|
|
}
|
|
|
|
do_test "$@"
|