7233e91af0
When the system is under heavy load, it can happen that the unit cache is refreshed for an unrelated reason (in the test I simulate this by attempting to start a non-existing unit). The new unit is found and accounted for in the cache, but it's ignored since we are loading something else. When we actually look for it, by attempting to start it, the cache is up to date so no refresh happens, and starting fails although we have it loaded in the cache. When the unit state is set to UNIT_NOT_FOUND, mark the timestamp in u->fragment_loadtime. Then when attempting to load again we can check both if the cache itself needs a refresh, OR if it was refreshed AFTER the last failed attempt that resulted in the state being UNIT_NOT_FOUND. Update the test so that this issue reproduces more often. |
||
---|---|---|
.. | ||
fuzz | ||
hwdb.d | ||
journal-data | ||
mocks | ||
TEST-01-BASIC | ||
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 | ||
TEST-11-ISSUE-3166 | ||
TEST-12-ISSUE-3171 | ||
TEST-13-NSPAWN-SMOKE | ||
TEST-14-MACHINE-ID | ||
TEST-15-DROPIN | ||
TEST-16-EXTEND-TIMEOUT | ||
TEST-17-UDEV-WANTS | ||
TEST-18-FAILUREACTION | ||
TEST-19-DELEGATE | ||
TEST-20-MAINPIDGAMES | ||
TEST-21-SYSUSERS | ||
TEST-22-TMPFILES | ||
TEST-23-TYPE-EXEC | ||
TEST-24-UNIT-TESTS | ||
TEST-25-IMPORT | ||
TEST-26-SETENV | ||
TEST-27-STDOUTFILE | ||
TEST-28-PERCENTJ-WANTEDBY | ||
TEST-29-UDEV-ID_RENAMING | ||
TEST-30-ONCLOCKCHANGE | ||
TEST-31-DEVICE-ENUMERATION | ||
TEST-32-OOMPOLICY | ||
TEST-33-CLEAN-UNIT | ||
TEST-34-DYNAMICUSERMIGRATE | ||
TEST-36-NUMAPOLICY | ||
TEST-37-RUNTIMEDIRECTORYPRESERVE | ||
TEST-38-FREEZER | ||
TEST-39-EXECRELOAD | ||
TEST-40-EXEC-COMMAND-EX | ||
TEST-41-ONESHOT-RESTART | ||
TEST-42-EXECSTOPPOST | ||
TEST-43-PRIVATEUSER-UNPRIV | ||
TEST-44-LOG-NAMESPACE | ||
TEST-46-HOMED | ||
TEST-47-ISSUE-14566 | ||
TEST-48-START-STOP-NO-RELOAD | ||
TEST-49-UDEV-EVENT-TIMEOUT | ||
TEST-50-DISSECT | ||
TEST-51-ISSUE-16115 | ||
TEST-52-HONORFIRSTSHUTDOWN | ||
test-execute | ||
test-network | ||
test-network-generator-conversion | ||
test-path | ||
test-resolve | ||
test-umount | ||
testsuite-04.units | ||
testsuite-06.units | ||
testsuite-08.units | ||
testsuite-10.units | ||
testsuite-11.units | ||
testsuite-16.units | ||
testsuite-28.units | ||
testsuite-30.units/systemd-timedated.service.d | ||
testsuite-52.units | ||
units | ||
.gitignore | ||
create-busybox-container | ||
create-sys-script.py | ||
hwdb-test.sh | ||
meson.build | ||
mkosi.build.networkd-test | ||
mkosi.default.networkd-test | ||
mkosi.nspawn.networkd-test | ||
networkd-test.py | ||
README.testsuite | ||
rule-syntax-check.py | ||
run-integration-tests.sh | ||
run-unit-tests.py | ||
splash.bmp | ||
sys-script.py | ||
sysv-generator-test.py | ||
test-efi-create-disk.sh | ||
test-exec-deserialization.py | ||
test-functions | ||
test-network-generator-conversion.sh | ||
testdata | ||
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: $ ninja -C build # Avoid building anything as root later $ sudo test/run-integration-tests.sh ninja: Entering directory `/home/zbyszek/src/systemd/build' ninja: no work to do. --x-- Running TEST-01-BASIC --x-- + make -C TEST-01-BASIC BUILD_DIR=/home/zbyszek/src/systemd/build clean setup run make: Entering directory '/home/zbyszek/src/systemd/test/TEST-01-BASIC' TEST-01-BASIC CLEANUP: Basic systemd setup TEST-01-BASIC SETUP: Basic systemd setup ... TEST-01-BASIC RUN: Basic systemd setup [OK] make: Leaving directory '/home/zbyszek/src/systemd/test/TEST-01-BASIC' --x-- Result of TEST-01-BASIC: 0 --x-- --x-- Running TEST-02-CRYPTSETUP --x-- + make -C TEST-02-CRYPTSETUP BUILD_DIR=/home/zbyszek/src/systemd/build clean setup run If one of the tests fails, then $subdir/test.log contains the log file of the test. To run just one of the cases: $ sudo make -C test/TEST-01-BASIC clean setup run Specifying the build directory ============================== If the build directory is not detected automatically, it can be specified with BUILD_DIR=: $ sudo BUILD_DIR=some-other-build/ test/run-integration-tests or $ sudo make -C test/TEST-01-BASIC BUILD_DIR=../../some-other-build/ ... Note that in the second case, the path is relative to the test case directory. An absolute path may also be used in both cases. Configuration variables ======================= TEST_NO_QEMU=1 Don't run tests under QEMU TEST_NO_NSPAWN=1 Don't run tests under systemd-nspawn TEST_NO_KVM=1 Disable QEMU KVM auto-detection (may be necessary when you're trying to run the *vanilla* QEMU and have both qemu and qemu-kvm installed) TEST_NESTED_KVM=1 Allow tests to run with nested KVM. By default, the testsuite disables nested KVM if the host machine already runs under KVM. Setting this variable disables such checks QEMU_MEM=512M Configure amount of memory for QEMU VMs (defaults to 512M) QEMU_SMP=1 Configure number of CPUs for QEMU VMs (defaults to 1) KERNEL_APPEND='...' Append additional parameters to the kernel command line NSPAWN_ARGUMENTS='...' Specify additional arguments for systemd-nspawn QEMU_TIMEOUT=infinity Set a timeout for tests under QEMU (defaults to infinity) NSPAWN_TIMEOUT=infinity Set a timeout for tests under systemd-nspawn (defaults to infinity) INTERACTIVE_DEBUG=1 Configure the machine to be more *user-friendly* for interactive debuggung (e.g. by setting a usable default terminal, suppressing the shutdown after the test, etc.) The kernel and initramfs can be specified with $KERNEL_BIN and $INITRD. (Fedora's or Debian's default kernel path and initramfs are used by default) A script will try to find your QEMU binary. If you want to specify a different one with $QEMU_BIN. Debugging the qemu image ======================== If you want to log in the testsuite virtual machine, you can specify additional kernel command line parameter with $KERNEL_APPEND and then log in as root. $ sudo make -C test/TEST-01-BASIC KERNEL_APPEND="systemd.unit=multi-user.target" run Root password is empty. Ubuntu CI ========= New PR submitted to the project are run through regression tests, and one set of those is the 'autopkgtest' runs for several different architectures, called 'Ubuntu CI'. Part of that testing is to run all these tests. Sometimes these tests are temporarily blacklisted from running in the 'autopkgtest' tests while debugging a flaky test; that is done by creating a file in the test directory named 'blacklist-ubuntu-ci', for example to prevent the TEST-01-BASIC test from running in the 'autopkgtest' runs, create the file 'TEST-01-BASIC/blacklist-ubuntu-ci'. The tests may be disabled only for specific archs, by creating a blacklist file with the arch name at the end, e.g. 'TEST-01-BASIC/blacklist-ubuntu-ci-arm64' to disable the TEST-01-BASIC test only on test runs for the 'arm64' architecture. Note the arch naming is not from 'uname -m', it is Debian arch names: https://wiki.debian.org/ArchitectureSpecificsMemo For PRs that fix a currently blacklisted test, the PR should include removal of the blacklist file.