mirror of
https://github.com/systemd/systemd.git
synced 2024-11-02 10:51:20 +03:00
| .. | ||
| TEST-01-BASIC | ||
| .gitignore | ||
| a.service | ||
| b.service | ||
| c.service | ||
| d.service | ||
| e.service | ||
| f.service | ||
| g.service | ||
| h.service | ||
| Makefile | ||
| README.testsuite | ||
| rule-syntax-check.py | ||
| rules-test.sh | ||
| sys.tar.xz | ||
| test-functions | ||
| udev-test.pl | ||
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 $ 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 Making all in docs/libudev Making all in docs/gudev 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 If you want to log in the testsuite virtual machine, you can specify additional kernel command line parameter with $DEBUGFAIL. $ sudo sh -c 'DEBUGFAIL="systemd.unit=multi-user.target" make clean setup run' you can even skip the "clean" and "setup" if you want to run the machine again. $ sudo sh -c 'DEBUGFAIL="systemd.unit=multi-user.target" make run'