| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixes #6685.
|
|\
| |
| | |
DHCPv6: Add support to send MUD URL
|
| | |
|
|\ \
| | |
| | | |
Make homed/userdbd/repart services installable (to allow uninstalling)
|
| | |
| | |
| | |
| | | |
This way it's easier to see when a wrong $BUILD_DIR was passed.
|
| | |
| | |
| | |
| | | |
Fixes #15083. Users might want to disable homed if not used to save resources.
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
DHCP4: Add support to emit and receive SMTP servers.
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Functional test rework
|
| | | |
|
| | |
| | |
| | |
| | | |
This should help catch this class of errors.
|
| | |
| | |
| | |
| | |
| | |
| | | |
It is more trouble than it is worth. The setup is of a loopback device
is very quick, so it's better to always create it when needed and
immediately drop afterwards.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This causes the unprivileged-nspawn-root directory to be removed
after running one test. The advantage is that we reduce the maximum
disk-space use quite a bit (47*400 MB → about 18GB).
|
| | |
| | |
| | |
| | |
| | |
| | | |
has-overflow was a temporary hack that was removed in
844da987ef8b8c98f837d3328eeb3ed481f43835 (Oct. 2016). All the makefiles
can be the same, and all the targets can be handled identically.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Before, we'd copy the test tree into nspawn-root, and run the tests from there.
This is OK, and doesn't actually take much extra time. But it uses quite a lot
of extra disk space. So let's make things a bit more efficient by running
directly from the image file.
We still run the unprivileged nspawn tests from a copy. Once the kernel
implements fs shift, we can do away with that too.
|
| | |
| | |
| | |
| | | |
Otherwise they accumulate and create noise.
|
| | |
| | |
| | |
| | |
| | | |
Sometimes it is not clear from the preceding output that there was a
failure.
|
| | |
| | |
| | |
| | |
| | | |
This is useful for sanitizer builds under CI, see
https://github.com/systemd/systemd-centos-ci/pull/202#issuecomment-566476592.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Before, we'd create a separate image for each test, in
/var/tmp/systemd-test.XXXXX/rootdisk.img. Most of the images
where very similar, except that each one had some unit files installed
specifically for the test. The installation of those custom unit files
was removed in previous commits (all the unit files are always installed).
The new approach is to only create as few distinct images as possible.
We have:
default.img: the "normal" image suitable for almost all the tests
basic.img: the same as default image but doesn't mask any services
cryptsetup.img: p2 is used for encrypted /var
badid.img: /etc/machine-id is overwritten with stuff
selinux.img: with selinux added for fun and fun
and a few others:
ls -l build/test/*img
lrwxrwxrwx 1 root root 38 Mar 21 21:23 build/test/badid.img -> /var/tmp/systemd-test.PJFFeo/badid.img
lrwxrwxrwx 1 root root 38 Mar 21 21:17 build/test/basic.img -> /var/tmp/systemd-test.na0xOI/basic.img
lrwxrwxrwx 1 root root 43 Mar 21 21:18 build/test/cryptsetup.img -> /var/tmp/systemd-test.Tzjv06/cryptsetup.img
lrwxrwxrwx 1 root root 40 Mar 21 21:19 build/test/default.img -> /var/tmp/systemd-test.EscAsS/default.img
lrwxrwxrwx 1 root root 39 Mar 21 21:22 build/test/nspawn.img -> /var/tmp/systemd-test.HSebKo/nspawn.img
lrwxrwxrwx 1 root root 40 Mar 21 21:20 build/test/selinux.img -> /var/tmp/systemd-test.daBjbx/selinux.img
lrwxrwxrwx 1 root root 39 Mar 21 21:21 build/test/test08.img -> /var/tmp/systemd-test.OgnN8Z/test08.img
I considered trying to use the same image everywhere. It would probably be
possible, but it would be very brittle. By using separate images where it is
necessary we keep various orthogonal modifications independent.
The way that images are cached is complicated by the fact that we still
want to keep them in /var/tmp. Thus, an image is created on first use and
linked to from build/test/ so it can be found by other tests.
Tests cannot be run in parallel. I think that is an acceptable limitation.
Creation of the images was probably taking more resources then the actual
tests, so we should be better off anyway.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
We had an fstab for the sole purpose of remounting "/" rw. Mounting root ro
is a pointless excercise in obsolete approaches. More importantly, the nspawn
image is now the same as the qemu one.
|
| | |
| | |
| | |
| | | |
p2 is only used in the cryptsetup test...
|
| | | |
|
| | |
| | |
| | |
| | | |
Now we will run setup_nspawn_root() in some case where do don't need to.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
On my laptop, it now takes 0.23 s. We don't need the overhead of creating
an image and spawning a machine to mangle a file in /tmp.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Setup of lingering is dropped. I don't think it's necessary for anything,
because the unit is still pulled in from the testsuite service.
|
| | | |
|
| | |
| | |
| | |
| | | |
If the test was run a second time from the same root, it would fail.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This way we always start with a clean slate when running the test
repeatedly.
|
| | |
| | |
| | |
| | | |
No need to call setup_nspawn_root() if we plan to only run under qemu.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
The two timezone files are now installed in the global setup. I am not too
happy about this, but it still seems better than to create a completely
separate image just for this.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Also run mask_supporting_services() here.
|