mirror of
https://github.com/systemd/systemd.git
synced 2024-12-23 21:35:11 +03:00
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.
56 lines
1.2 KiB
Bash
Executable File
56 lines
1.2 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
set -v -x
|
|
|
|
rm -f /test.log
|
|
|
|
TL=/test.log.XXXXXXXX
|
|
|
|
function wait_for()
|
|
{
|
|
service=${1}
|
|
result=${2:-success}
|
|
time=${3:-45}
|
|
|
|
while [[ ! -f /${service}.terminated && ! -f /${service}.success && $time -gt 0 ]]
|
|
do
|
|
sleep 1
|
|
time=$(( $time - 1 ))
|
|
done
|
|
|
|
if [[ ! -f /${service}.${result} ]]
|
|
then
|
|
journalctl -u testsuite-${service/_/-}.service >> "${TL}"
|
|
fi
|
|
}
|
|
|
|
# This checks all stages, start, runtime and stop, can be extended by
|
|
# EXTEND_TIMEOUT_USEC
|
|
|
|
wait_for success_all
|
|
|
|
# These check that EXTEND_TIMEOUT_USEC that occurs at greater than the
|
|
# extend timeout interval but less then the stage limit (TimeoutStartSec,
|
|
# RuntimeMaxSec, TimeoutStopSec) still succeed.
|
|
|
|
wait_for success_start
|
|
wait_for success_runtime
|
|
wait_for success_stop
|
|
|
|
# These ensure that EXTEND_TIMEOUT_USEC will still timeout in the
|
|
# approprate stage, after the stage limit, when the EXTEND_TIMEOUT_USEC
|
|
# message isn't sent within the extend timeout interval.
|
|
|
|
wait_for fail_start startfail
|
|
wait_for fail_stop stopfail
|
|
wait_for fail_runtime runtimefail
|
|
|
|
if [[ -f "${TL}" ]]
|
|
then
|
|
# no mv
|
|
cp "${TL}" /test.log
|
|
exit 1
|
|
else
|
|
touch /testok
|
|
exit 0
|
|
fi
|