mirror of
https://github.com/systemd/systemd.git
synced 2024-11-02 10:51:20 +03:00
7fb4ee7aa5
Sometimes the ldconfig.service might take a bit longer to finish, causing spurious test timeouts: ``` [ 1025.858923] systemd[24]: ldconfig.service: Executing: /sbin/ldconfig -X ... [ 1043.883620] systemd[1]: ldconfig.service: Main process exited, code=exited, status=0/SUCCESS (success) ... Trying to halt container. Send SIGTERM again to trigger immediate termination. Container TEST-52-HONORFIRSTSHUTDOWN terminated by signal KILL. E: Test timed out after 20s ```
28 lines
905 B
Bash
Executable File
28 lines
905 B
Bash
Executable File
#!/bin/bash
|
|
set -e
|
|
|
|
TEST_REQUIRE_INSTALL_TESTS=0
|
|
TEST_DESCRIPTION="testing honor first shutdown"
|
|
TEST_NO_QEMU=1
|
|
|
|
# shellcheck source=test/test-functions
|
|
. "${TEST_BASE_DIR:?}/test-functions"
|
|
|
|
# Using timeout because if the test fails it can loop.
|
|
# The reason is because the poweroff executed by end.service
|
|
# could turn into a reboot if the test fails.
|
|
NSPAWN_TIMEOUT=60
|
|
|
|
# Remove this file if it exists. This is used along with
|
|
# the make target "finish". Since concrete confirmation is
|
|
# only found from the console during the poweroff.
|
|
rm -f /tmp/honorfirstshutdown.log >/dev/null
|
|
|
|
check_result_nspawn_hook() {
|
|
grep -q "Shutdown is already active. Skipping emergency action request" /tmp/honorfirstshutdown.log
|
|
}
|
|
|
|
# Note: don't use a pipe in the following expression, as it breaks the trap
|
|
# handlers we have defined in test/test-functions.
|
|
do_test "$@" > >(tee /tmp/honorfirstshutdown.log)
|