mirror of https://github.com/morgan9e/systemd synced 2026-04-14 00:14:32 +09:00

Files

Daan De Meyer d9f48358bd test: Make it possible to run the integration tests standalone

Currently, to run the integration tests, it's still necessary to
install various other build tools besides meson: A compiler, gperf,
libcap, ... which we want to avoid in CI systems where we receive
prebuilt systemd packages and only want to test them. Examples are
Debian's autopkgtest CI and Fedora CI. Let's make it possible for
these systems to run the integration tests without having to install
any other build dependency besides meson by extracting the logic
required to run the integration tests with meson into a separate
subdirectory and adding a standalone top-level meson.build file which
can be used to configure a meson tree with as its only purpose running
the integration tests.

Practically, we do the following:
- all the integration test directories and integration-test-wrapper.py
  are moved from test/ to test/integration-test/.
- All the installation logic is kept out of test/integration-test/ or
  any of its subdirectories and moved into test/meson.build instead.
- We add test/integration-test/standalone/meson.build to run the
  integration tests standalone. This meson file includes
  test/integration-test via a cute symlink hack to trick meson into
  including a parent directory with subdir().
- Documentation is included on how to use the new standalone mode.
- TEST-64-UDEV-STORAGE and TEST-85-NETWORK are changed to generate separate
  units for each testcase to make them behave more like the other integration
  tests.

2025-03-27 21:37:13 +01:00

4.1 KiB

Raw Blame History

title, category, layout, SPDX-License-Identifier

title	category	layout	SPDX-License-Identifier
Code Quality Tools	Contributing	default	LGPL-2.1-or-later

Code Quality Tools

The systemd project has a number of code quality tools set up in the source tree and on the github infrastructure. Here's an incomprehensive list of the available functionality:

Use meson test -C build to run the unit tests. Some tests are skipped if no privileges are available, hence consider also running them with sudo meson test -C build. A couple of unit tests are considered "unsafe" (as they change system state); to run those too, build with meson setup -Dtests=unsafe. Finally, some unit tests are considered to be very slow, build them too with meson setup -Dslow-tests=true. (Note that there are a couple of manual tests in addition to these unit tests.) (Also note: you can change these flags for an already set up build tree, too, with "meson configure -C build -D…".)
Run the full integration test suite as described in test/integration-tests/README.md. This will build OS images with a number of integration tests and run them using systemd-nspawn and qemu. Requires root.
Use ./coccinelle/run-coccinelle.sh to run all Coccinelle semantic patch scripts we ship. The output will show false positives, hence take it with a pinch of salt.
Use ./tools/find-double-newline.sh recdiff to find double newlines. Use ./tools/find-double-newline.sh recpatch to fix them. Take this with a grain of salt, in particular as we generally leave foreign header files we include in our tree unmodified, if possible.
Similar use ./tools/find-tabs.sh recdiff to find TABs, and ./tools/find-tabs.sh recpatch to fix them. (Again, grain of salt, foreign headers should usually be left unmodified.)
Use ninja -C build check-api-docs to compare the list of exported symbols of libsystemd.so and libudev.so with the list of man pages. Symbols lacking documentation are highlighted.
Use ninja -C build update-hwdb and ninja -C build update-hwdb-autosuspend to automatically download and import the PCI, USB, and OUI databases and the autosuspend quirks into the hwdb.
Use ninja -C build update-man-rules to update the meson rules for building man pages automatically from the docbook XML files included in man/.
There are multiple CI systems in use that run on every github pull request submission or update.
Coverity is analyzing systemd main branch in regular intervals. The reports are available online.
OSS-Fuzz is continuously fuzzing the codebase. Reports are available online. It also builds coverage reports daily.
Our tree includes .editorconfig, .dir-locals.el and .vimrc files, to ensure that editors follow the right indentiation styles automatically.
When building systemd from a git checkout the build scripts will automatically enable a git commit hook that ensures whitespace cleanliness.
CodeQL analyzes each PR and every commit pushed to main. The list of active alerts can be found here.
Each PR is automatically tested with Address Sanitizer and Undefined Behavior Sanitizer. See Testing systemd using sanitizers for more information.
Fossies provides source code misspelling reports. The systemd report can be found here.

Access to Coverity and oss-fuzz reports is limited. Please reach out to the maintainers if you need access.

4.1 KiB Raw Blame History

Code Quality Tools

4.1 KiB

Raw Blame History