238ddac165
lcov 2.1 introduced additional consistency checks [0] which make it trip over our coverage results quite often: Summary coverage rate: source files: 915 lines.......: 36.9% (78950 of 214010 lines) functions...: 53.3% (6906 of 12949 functions) Message summary: 73 warning messages: inconsistent: 73 lcov: ERROR: (corrupt) unable to read trace file '/var/tmp/systemd-test-TEST-04-JOURNAL/coverage-info.new': lcov: ERROR: (inconsistent) "/build/src/shutdown/umount.c":298: function 'umount_with_timeout' is not hit but line 317 is. To skip consistency checks, see the 'check_data_consistency' section in man lcovrc(5). (use "lcov --ignore-errors inconsistent ..." to bypass this error) (use "lcov --ignore-errors corrupt ..." to bypass this error) This is caused by coverage collected during shutdown which is a bit unreliable, especially towards the final shutdown stage(s). Let's just ignore the consistency errors for now. [0] https://github.com/linux-test-project/lcov/releases/tag/v2.2 |
||
---|---|---|
.clusterfuzzlite | ||
.github | ||
.semaphore | ||
catalog | ||
coccinelle | ||
docs | ||
factory | ||
hwdb.d | ||
LICENSES | ||
man | ||
mime | ||
mkosi.conf.d | ||
mkosi.extra | ||
mkosi.images | ||
mkosi.repart | ||
mkosi.sanitizers | ||
mkosi.uki-profiles | ||
modprobe.d | ||
network | ||
po | ||
presets | ||
profile.d | ||
rules.d | ||
shell-completion | ||
src | ||
sysctl.d | ||
sysusers.d | ||
test | ||
tmpfiles.d | ||
tools | ||
units | ||
xorg | ||
.clang-format | ||
.ctags | ||
.dir-locals.el | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
.mailmap | ||
.packit.yml | ||
.pylintrc | ||
.vimrc | ||
.ycm_extra_conf.py | ||
LICENSE.GPL2 | ||
LICENSE.LGPL2.1 | ||
meson_options.txt | ||
meson.build | ||
meson.version | ||
mkosi.clangd | ||
mkosi.clean | ||
mkosi.conf | ||
mkosi.coredump-journal-storage.conf | ||
mkosi.functions | ||
mkosi.leak-sanitizer-suppressions | ||
mkosi.postinst.chroot | ||
NEWS | ||
README | ||
README.md | ||
TODO |
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack