| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
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.
|
|\ \ \
| |_|/
|/| | |
locale: verify loaded keymap or friends
|
| |/ |
|
|\ \
| | |
| | | |
test: add a couple of tests for userdbctl
|
| |/ |
|
|\ \
| | |
| | | |
test: don't expand the subshell expression prematurely
|
| | |
| | |
| | |
| | | |
Return code of the EXIT trap handler is ignored in bash.
|
| | |
| | |
| | |
| | | |
As it is already handled by the "main" script (testsuite-74.sh).
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We need to expand the subshell expression during the `bash -c`
invocation, not before, to take the desired effect, as now it expands to:
timeout 30 bash -c 'while [[ 0 -eq 0 ]]; do sleep 1; done'
instead of the expected:
timeout 30 bash -c 'while [[ $(coredumpctl list -q --no-legend 770 | wc -l) -eq 0 ]]; do sleep 1; done'
Follow-up to aadbd81f7f.
|
| |
| |
| |
| |
| |
| |
| | |
So we don't have to do this twice - once for the base report and then
for each "real" one.
Follow-up to 7fdd6e157a.
|
|/
|
|
|
|
|
|
|
|
| |
I noticed that our coverage reports miss some files completely - this
happens when the test doesn't touch the code in them at all, so the
generated coverage data (and resulting reports) have no information
about them. Let's fix this by doing an initial zero coverage capture
that contains a zeroed counter for every instrumented line in every
file, so when we later merge it with a capture from the test, it shows up
with a missing coverage instead of not showing at all.
|
| |
|
|
|
|
|
|
|
|
| |
The test files are /proc//auxv files copies from various architecutres
signified by the file name suffix.
Those tests are fairly simple, but when we run them on n architectures, we do
~n² cross-arch tests.
|
|\
| |
| | |
core: support overriding NOTIFYACCESS= through sd-notify during runtime
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
The nvme by-id symlink changes to the latest namespace when a new namespace gets
added, for example by connecting multiple NVMe/TCP host controllers via nvme
connect-all.
That is incorrect for persistent device links.
The persistent symbolic device link should continue to point to the same NVMe
namespace throughout the lifetime of the current boot.
Therefore the namespace id needs to be added to the link name.
|
|
|
|
|
|
|
| |
Log an error when a rule line contains the following kind of conflicting
match expressions:
KEY=="foo", KEY=="bar"
|
|
|
|
|
|
|
| |
Fix check for conflicting and duplicate expressions of types that
support alternative patterns.
Fixes: 3ec58d0cd8f6 ("udev-rules: check for conflicting and duplicate expressions")
|
|
|
|
|
|
|
|
|
|
|
| |
For some unknown reasons, the temporary directory created by the test
below is not removed:
```
# Test the case that a valid symlink is in the path.
label = 'valid_symlink-deep'
test_content('f= {} - - - - ' + label, label, user=user, subpath='/deep/1/2', path_cb=valid_symlink)
```
To keep /tmp clean, let's create the global temprary directory.
|
| |
|
|\
| |
| | |
udev: slightly extend comment and add more tests
|
| | |
|
|\ \
| | |
| | | |
udevadm-verify: print a short summary
|
| | | |
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
machinectl: add verb edit and cat to operate on .nspawn files
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Make sure /etc/udev/hwdb.d/ exists before creating a file inside it.
Fixes: 95cf8cae77f7 ("test: add coverage test for udevadm")
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
Log an error when a rule line contains conflicting match expressions, e.g.
NAME=="value", NAME!="value"
Log a warning when a rule line contains duplicate expressions, e.g.
NAME=="value", NAME=="value"
|
|\ \
| | |
| | | |
Fixes for test 58 repart
|
| | |
| | |
| | |
| | |
| | |
| | | |
Let image_install figures the binary paths out itself as not all distributions
ship the mkfs.* tools in the same location. For example openSUSE ships
mksquashfs in /usr/bin/.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
ProtectControlGroups=yes
The interface requires services to write to the cgroup file to activate notifications,
but with ProtectControlGroups=yes we make it read-only. Add a writable bind mount.
Follow-up for 6bb0084204bd93122c9f04391b80aea5a8a0ff08
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
directory
This avoids hard coding the path of the directory where the unit tests are
installed.
|