systemd/test/units/testsuite-47.sh

#!/usr/bin/env bash
set -eux
set -o pipefail

systemd-analyze log-level debug
systemd-analyze log-target console

systemctl start testsuite-47-repro
sleep 4
systemctl status testsuite-47-repro

leaked_pid=$(cat /leakedtestpid)

systemctl stop testsuite-47-repro
sleep 4

# Leaked PID will still be around if we're buggy.
# I personally prefer to see 42.
ps -p "$leaked_pid" && exit 42

systemd-analyze log-level info

echo OK >/testok

exit 0
test: move TEST-47-* to static files 2020-03-20 21:57:54 +03:00			`#!/usr/bin/env bash`
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`
core: transition to FINAL_SIGTERM state after ExecStopPost= Fixes #14566 2020-01-25 18:46:16 +03:00			`set -o pipefail`

			`systemd-analyze log-level debug`
			`systemd-analyze log-target console`

test: move TEST-47-* to static files 2020-03-20 21:57:54 +03:00			`systemctl start testsuite-47-repro`
test: bump the TEST-47 sleeps once again Several recent failed runs show that the test is still racy in two ways: 1) Sometimes it takes a while before the PID file is created, leading to: ``` [ 10.950540] testsuite-47.sh[308]: ++ cat /leakedtestpid [ 10.959712] testsuite-47.sh[308]: cat: /leakedtestpid: No such file or directory [ 10.959824] testsuite-47.sh[298]: + leaked_pid= ``` 2) Again, sometimes we check the leaked PID before the unit is actually stopped, leading to a false negative: ``` [ 18.099599] testsuite-47.sh[346]: ++ cat /leakedtestpid [ 18.116462] testsuite-47.sh[333]: + leaked_pid=342 [ 18.117101] testsuite-47.sh[333]: + systemctl stop testsuite-47-repro ... [ 20.033907] testsuite-47.sh[333]: + ps -p 342 [ 20.080050] testsuite-47.sh[351]: PID TTY TIME CMD [ 20.080050] testsuite-47.sh[351]: 342 ? 00:00:00 sleep [ 20.082040] testsuite-47.sh[333]: + exit 42 ``` 2020-07-08 15:42:43 +03:00			`sleep 4`
test: move TEST-47-* to static files 2020-03-20 21:57:54 +03:00			`systemctl status testsuite-47-repro`
core: transition to FINAL_SIGTERM state after ExecStopPost= Fixes #14566 2020-01-25 18:46:16 +03:00
			`leaked_pid=$(cat /leakedtestpid)`

test: move TEST-47-* to static files 2020-03-20 21:57:54 +03:00			`systemctl stop testsuite-47-repro`
test: bump the TEST-47 sleeps once again Several recent failed runs show that the test is still racy in two ways: 1) Sometimes it takes a while before the PID file is created, leading to: ``` [ 10.950540] testsuite-47.sh[308]: ++ cat /leakedtestpid [ 10.959712] testsuite-47.sh[308]: cat: /leakedtestpid: No such file or directory [ 10.959824] testsuite-47.sh[298]: + leaked_pid= ``` 2) Again, sometimes we check the leaked PID before the unit is actually stopped, leading to a false negative: ``` [ 18.099599] testsuite-47.sh[346]: ++ cat /leakedtestpid [ 18.116462] testsuite-47.sh[333]: + leaked_pid=342 [ 18.117101] testsuite-47.sh[333]: + systemctl stop testsuite-47-repro ... [ 20.033907] testsuite-47.sh[333]: + ps -p 342 [ 20.080050] testsuite-47.sh[351]: PID TTY TIME CMD [ 20.080050] testsuite-47.sh[351]: 342 ? 00:00:00 sleep [ 20.082040] testsuite-47.sh[333]: + exit 42 ``` 2020-07-08 15:42:43 +03:00			`sleep 4`
core: transition to FINAL_SIGTERM state after ExecStopPost= Fixes #14566 2020-01-25 18:46:16 +03:00
			`# Leaked PID will still be around if we're buggy.`
			`# I personally prefer to see 42.`
			`ps -p "$leaked_pid" && exit 42`

			`systemd-analyze log-level info`

TEST-*: use spacing before redirection operator, but not after << EOF → <<EOF > foo < bar → >foo <bar 2021-04-08 01:09:55 +03:00			`echo OK >/testok`
core: transition to FINAL_SIGTERM state after ExecStopPost= Fixes #14566 2020-01-25 18:46:16 +03:00
			`exit 0`