1
0
mirror of https://github.com/systemd/systemd.git synced 2024-11-07 01:27:11 +03:00
systemd/test
Daniel Black a327431bd1 core: add EXTEND_TIMEOUT_USEC={usec} - prevent timeouts in startup/runtime/shutdown (#7214)
With Type=notify services, EXTEND_TIMEOUT_USEC= messages will delay any startup/
runtime/shutdown timeouts.

A service that hasn't timed out, i.e, start time < TimeStartSec,
runtime < RuntimeMaxSec and stop time < TimeoutStopSec, may by sending
EXTEND_TIMEOUT_USEC=, allow the service to continue beyond the limit for
the execution phase (i.e TimeStartSec, RunTimeMaxSec and TimeoutStopSec).

EXTEND_TIMEOUT_USEC= must continue to be sent (in the same way as
WATCHDOG=1) within the time interval specified to continue to reprevent
the timeout from occuring.

Watchdog timeouts are also extended if a EXTEND_TIMEOUT_USEC is greater
than the remaining time on the watchdog counter.

Fixes #5868.
2017-12-14 12:17:43 +01:00
..
hwdb
journal-data
loopy.service.d
mocks
TEST-01-BASIC tests: try to autodetect directory better 2017-12-06 15:16:35 +01:00
TEST-02-CRYPTSETUP
TEST-03-JOBS
TEST-04-JOURNAL
TEST-05-RLIMITS
TEST-06-SELINUX
TEST-07-ISSUE-1981
TEST-08-ISSUE-2730
TEST-09-ISSUE-2691
TEST-10-ISSUE-2467 tests: don't use "netcat" for testing TEST-10-ISSUE-2467 2017-12-05 13:49:13 +01:00
TEST-11-ISSUE-3166
TEST-12-ISSUE-3171
TEST-13-NSPAWN-SMOKE tests: try to autodetect directory better 2017-12-06 15:16:35 +01:00
TEST-14-MACHINE-ID tests: fix description of TEST-14-MACHINE-ID 2017-11-29 12:34:12 +01:00
TEST-15-DROPIN
TEST-16-EXTEND-TIMEOUT core: add EXTEND_TIMEOUT_USEC={usec} - prevent timeouts in startup/runtime/shutdown (#7214) 2017-12-14 12:17:43 +01:00
TEST-17-UDEV-WANTS tests: try to autodetect directory better 2017-12-06 15:16:35 +01:00
TEST-18-FAILUREACTION tests: try to autodetect directory better 2017-12-06 15:16:35 +01:00
TEST-19-DELEGATE tests: try to autodetect directory better 2017-12-06 15:16:35 +01:00
test-execute test-execute: use the "nogroup" group if it exists for testing 2017-12-06 13:40:50 +01:00
test-path
test-resolve
.gitignore
a.service
b.service
basic.target
c.service
create-sys-script.py
d.service
daughter.service
e.service
end.service
f.service
g.service
grandchild.service
h.service
hello-after-sleep.target
hello.service
hwdb-test.sh test: set log_level to info in test-hwdb and check-help-* 2017-11-26 00:01:55 +09:00
loopy2.service
loopy3.service
loopy4.service
loopy.service
meson.build test-execute: use the "nogroup" group if it exists for testing 2017-12-06 13:40:50 +01:00
networkd-test.py
parent-deep.slice
parent.slice
README.testsuite
rule-syntax-check.py meson: re-attach rule-syntax-check.py test 2017-11-22 12:46:08 +01:00
run-integration-tests.sh run-integration-test: allow argument to be overriden 2017-12-06 15:16:55 +01:00
sched_idle_bad.service
sched_idle_ok.service
sched_rr_bad.service
sched_rr_change.service
sched_rr_ok.service
shutdown.target
sleep.service
sockets.target
son.service
splash.bmp
sys-script.py
sysinit.target
sysv-generator-test.py
test-efi-create-disk.sh
test-exec-deserialization.py
test-functions tests: install test as part of BASICTOOLS (#7434) 2017-11-23 13:28:12 +01:00
testsuite.target
timers.target
udev-test.pl
unstoppable.service

The extended testsuite only works with uid=0. It contains of several
subdirectories named "test/TEST-??-*", which are run one by one.

To run the extended testsuite do the following:

$ make all  # Avoid the "sudo make" below building anything as root
$ cd test
$ sudo make clean check
...
make[1]: Entering directory `/mnt/data/harald/git/systemd/test/TEST-01-BASIC'
Making all in .
Making all in po
TEST: Basic systemd setup [OK]
make[1]: Leaving directory `/mnt/data/harald/git/systemd/test/TEST-01-BASIC'
...

If one of the tests fails, then $subdir/test.log contains the log file of
the test.

To debug a special testcase of the testsuite do:

$ make all
$ cd test/TEST-01-BASIC
$ sudo make clean setup run

QEMU
====

If you want to log in the testsuite virtual machine, you can specify
additional kernel command line parameter with $KERNEL_APPEND.

$ sudo make KERNEL_APPEND="systemd.unit=multi-user.target" clean setup run

you can even skip the "clean" and "setup" if you want to run the machine again.

$ sudo make KERNEL_APPEND="systemd.unit=multi-user.target" run

You can specify a different kernel and initramfs with $KERNEL_BIN and $INITRD.
(Fedora's or Debian's default kernel path and initramfs are used by default)

$ sudo make KERNEL_BIN=/boot/vmlinuz-foo INITRD=/boot/initramfs-bar clean check

A script will try to find your QEMU binary. If you want to specify a different
one you can use $QEMU_BIN.

$ sudo make QEMU_BIN=/path/to/qemu/qemu-kvm clean check