| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
sd-journal: allow to specify compression algorithm through env
|
| |
| |
| |
| | |
compression algorithm
|
|\ \
| | |
| | | |
test: introduce TEST-81-GENERATORS
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add some explicit tests for various generators we ship, e.g.:
- systemd-debug-generator
- systemd-environment-d-generator
- systemd-fstab-generator
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
A simple test case for issue #27106.
Resolves: #27139
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
The rational is the same as the one described in commit
be0cc2ce6c947aafadb3f42dba405269f670b31c.
|
| |/
|/| |
|
| |
| |
| |
| |
| | |
When invoked by udevadm verify, warn about rules that have PROGRAM
assignments specified after RESULT checks.
|
|\ \
| |/
|/| |
Ensure sysexts do not contain an os-release file, do not load sysexts from /usr[/local]/lib/extensions/
|
| |
| |
| |
| |
| | |
sysexts are not supposed to ship os-release files, enforce this
when loading them
|
|\ \
| | |
| | | |
test: set ReadWritePaths= for test-.services when built w/ coverage
|
| | | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Let's make the dropin, to make the build dir writable for gcov, a bit
more generic, so it can be used by all units starting with prefix test-.
This should help with a bunch of recent reports about missing coverage I
got, as well as with existing test units using DynamicUser=true.
This might feel a bit like a magic trick from behind the curtains, but I
want to touch the actual tests as little as possible, since it makes them
unnecessarily messy (see the various workarounds for sanitizers), and
the coverage reports are generated only in a specific CI job anyway.
|
| |
| |
| |
| |
| |
| | |
This can be used to prepare an image for firstboot by removing all
files that systemd knows about that contain machine specific
information.
|
| |
| |
| |
| | |
This should fix shellcheck warning SC2004.
|
| |
| |
| |
| | |
Use in-line error handling rather than redirections. Follow up on #27020
|
|/
|
|
|
|
|
|
|
|
|
|
| |
systemd-repart needs to find mkfs.ext4 for the test.
This is located in the directory /usr/sbin on openSUSE Tumbleweed.
But since the variable ALWAYS_SET_PATH in /etc/login.defs is set to yes,
su re-initializes the $PATH variable and removes /usr/sbin.
Hence, mkfs.ext4 is not found and the test fails.
Using setpriv instead of su fixes this issue and is more appropriate to
do the switch user task from root.
[zjs: move setpriv to $BASICTOOLS and force-push to retrigger CI]
|
| |
|
|\
| |
| | |
mkosi: Update to latest
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Drop Netdev= as it was removed in mkosi
- Always install python-psutil in the final image (required for networkd tests)
- Always Install python-pytest in the final image (required for ukify tests)
- Use the narrow glob for all centos python packages
- Drop the networkd mkosi config files (the default image can be used instead)
- Use ".conf" as the mkosi config file suffix everywhere
- Copy src/ to /root/src in the final image and set gdb substitute path in
.gdbinit to make gdb work properly
|
| | |
|
|\ \
| |/
|/| |
systemd-cryptenroll: adding integration test cases
|
| | |
|
| |
| |
| |
| |
| |
| | |
Make sure the ENOENT exception reintroduced by commit
9db7081d83d56cd2523b03f9eb9d67ef1c93c55f is not applied when the parser
is invoked by udevadm verify.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes "sleep" invocations, and makes the notify access testcase a
lot more robust to runtime jitter. We use a pair of fifos in the fs to
sync instead.
Also various other improvoements, including comments.
(Also removes the unnecessary "no-qemu" restriction)
|
| |
| |
| |
| |
| |
| |
| | |
The test log is in the state directory, and we want to keep it around
when a test fails.
Follow-up for: 256a835f1c6c646a55039659aa2db186fbeb5c5d
|
|\ \
| | |
| | | |
Fix some shellcheck warnings
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Fixes for testsuite 74 mount
|
| | |
| | |
| | |
| | | |
Several whitespaces can separate "ext4" and "sd-mount-test" strings.
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is useful to identify log messages with metadata from the images
they run on. Look for ID/VERSION_ID/IMAGE_ID/IMAGE_VERSION/BUILD_ID,
with a SYSEXT_ prefix if we are looking at an extension, and append via
LogExtraFields= as respectively PORTABLE_NAME_AND_VERSION= in case of a
single image. In case of extensions, append as PORTABLE_ROOT_NAME_AND_VERSION=
for the base and one PORTABLE_EXTENSION_AND_VERSION= for each extension.
Example with a base and two extensions, with the unit coming from the
first extension:
[Service]
RootImage=/home/bluca/git/systemd/base.raw
Environment=PORTABLE=app0.raw
BindReadOnlyPaths=/etc/os-release:/run/host/os-release
LogExtraFields=PORTABLE=app0.raw
Environment=PORTABLE_ROOT=base.raw
LogExtraFields=PORTABLE_ROOT=base.raw
LogExtraFields=PORTABLE_ROOT_NAME_AND_VERSION=debian_10
ExtensionImages=/home/bluca/git/systemd/app0.raw
LogExtraFields=PORTABLE_EXTENSION=app0.raw
LogExtraFields=PORTABLE_EXTENSION_NAME_AND_VERSION=app_0
ExtensionImages=/home/bluca/git/systemd/app1.raw
LogExtraFields=PORTABLE_EXTENSION=app1.raw
LogExtraFields=PORTABLE_EXTENSION_NAME_AND_VERSION=app_1
|
|\ \
| | |
| | | |
Test fixlets
|
| | |
| | |
| | |
| | | |
It's not (and shouldn't be) used by any test scripts.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When testing the binaries from the host, make sure to not store the state data
below /usr but use a dedicated directory in /var/tmp/ instead.
The working directories of the tests, initially located in /var/tmp, are also
moved in a dedicated directory /var/tmp/systemd-tests.
|
|\ \ \
| | | |
| | | | |
test: explicitly pull in systemd-userdbd.service
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Since we don't run preset-all on the test image, the
systemd-userdbd.socket remains disabled. Let's pull it in explicitly
to give systemd-userdbd some coverage as well.
|
| | | |
| | | |
| | | |
| | | | |
Fixes: 25de7aa7b90c ("udev: modernize udev-rules.c")
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Log an error when a rule line contains the following kind of conflicting
match expressions:
KEY=="foo*", KEY=="bar*"
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When udev_rules_parse_file() is called by udevadm verify, issue warnings
about the following conditions in udev rules:
* the first token in the rule is preceded with a comma
* the last token in the rule is followed by a comma
* there is no comma between tokens
* there is no whitespace between tokens
* there is more than a single comma between tokens
* there is whitespace between a token and a comma
* there is no whitespace after comma
|
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | | |
Move unit tests in a dedicated subdir
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
only for TEST-02-UNITTESTS
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
installed in the same directory
testdata/ is shared by both the unit tests and the integration tests. Hence it
makes sense to place them right under /usr/lib/systemd/tests/ while the tests
themself are located under dedicated sub-directories:
/usr/lib/systemd/tests/
├── integration-tests
├── testdata
└── unit-tests
├── testdata -> ../testdata
However the unit tests implemented as shell scripts (such as
test-fstab-generator.sh) expect to find testdata/ where the scripts are
installed, ie they do something like:
src="$(dirname "$0")/testdata/test-fstab-generator"
This patch installs a symlink in 'unitestsdir' named "testdata" and that points
to whatever value 'testdata_dir' is set.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
/usr/lib/systemd/tests may contain more than the unit tests. For example on
SUSE we also install the integration tests there.
Putting the unit tests in a dedicated directory named 'unit-tests' makes the
layout cleaner.
Note that `run-unit-tests.py` has not been moved so we don't need to adjust
(Fedora) packaging and users also don't need to descend into the subdirectory.
|