| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This reverts commit 7d7bb5c8613b774bf77c531f46d31ee20d7a1b1e.
Still the CIs are flaky and the commit just slow down them.
|
|
|
|
|
| |
On Ubuntu CI, these don't exist because it tests installed
binaries, not just-built binaries.
|
|\
| |
| | |
resolvectl: support to modify interfaces managed by networkd
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Closes #10596
|
|\ \
| | |
| | | |
Minor fixes in test framework
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
without using -type f, the logs print an error such as:
E: E: modprobe: FATAL: Module asymmetric_keys not found in directory /lib/modules/4.15.0-54-generic
while this doesn't appear to cause problems, it can be extremely
distracting when trying to debug real failures.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
recognized"
The grep -v matches all lowercase, but "file" is captialized; just ignore case so
it's suppressed for either all lowercase or capital File.
|
| | |
| | |
| | |
| | | |
Also move TESTDIR and STATEFILE removal into test_cleanup
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Almost all tests were manually mounting/unmounting $TESTDIR/root
from the loopback image; this moves all that into test-functions
so the test setup functions are simplier.
Also add test_setup_cleanup() function, to cleanup what is mounted
by create_empty_image_rootdir()
|
|/ |
|
|\
| |
| |
| |
| | |
yuwata/network-do-not-set-routes-when-carrier-lost
network: do not configure routes when dropping addresses
|
| |
| |
| |
| |
| |
| | |
Even if addresses provided by DHCP is assigned, the state file may not
be written yet, or resolved may not receive the state change signal
yet, or resolved may not process the signal yet...
|
|/ |
|
|\
| |
| | |
network-generator: introduce new tool systemd-network-generator
|
| | |
|
| |
| |
| |
| |
| |
| | |
Previously, event if link's setup state is in failed, tests may pass,
as systemd-networkd-wait-online success if the state is in failed state.
This makes tests be checked more strictly.
|
|/ |
|
|
|
|
| |
broadcast
|
|
|
|
| |
Imported from networkd-test.py
|
|\
| |
| | |
network: reassign static routes and process reply address messages
|
| | |
|
|\ \
| | |
| | | |
network: rename Neighbor.MACAddress= and also support IPv4 address
|
| | | |
|
| | |
| | |
| | |
| | | |
Neighbor.MACAddress=
|
| | |
| | |
| | |
| | |
| | |
| | | |
And make it support IPv4 address.
Closes #13015.
|
|\ \ \
| |_|/
|/| | |
Refactor job ordering implementation (and fix cycle detection)
|
| | |
| | |
| | |
| | |
| | |
| | | |
job_compare return value is undefined in case the jobs have a loop
between them, so better make a test to make sure transaction cycle
detection catches it.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The test-engine Test2 tests the cycle detection when units a, b and d
all start at once
,-------------------after-----------------,
v |
a/start ---after---> d/start ---after---> b/start
Extend the test with Test11 that adds i.service which causes a and d
stop (by unordered Conflicts=) while starting b. Because stops precede
starts, we effectively eliminate the job cycle and all transaction jobs
should be applicable.
,-------------------after-----------------,
v |
a/stop <---after--- d/stop <---after--- b/start
. . ^
. . |
'. . . . . . . . . i/start ---after------'
|
| |/
|/| |
|
|\ \
| | |
| | | |
network: drop assertions about Tunnel.family
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
The test unexpectedly succeeds on KVM with sanitizer CI.
At least tentatively, let's drop the test.
|
|\ \ \
| |/ /
|/| | |
networkd: DHCPv6 - separate DHCPv6 options from DHCPv4 options
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
To keep the backward compatibility broken by the previous commit.
|
| | |
| | |
| | |
| | | |
Closes https://github.com/systemd/systemd/issues/12917
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
networkd does not manage loopback interface lo. So, previously, we have
no way to assign tunnel devices to lo.
|
|\ \ \
| | | |
| | | | |
Added support for xfrm interfaces
|
| |/ / |
|
|/ /
| |
| |
| |
| |
| | |
set_put() does not return -EEXIST.
Fixes #12995 and oss-fuzz#15678.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In Ubuntu CI, udev-test.pl is run from the debian/test/udev script,
in a test dir created for it; but udev-test.pl setup mounts a
dir, so if it doesn't cleanup/unmount before exiting, the test dir
autopkgtest created for it can't be removed, and autopkgtest
aborts the entire test suite, for example this output (from a
test run inside an armhf container):
autopkgtest [12:45:36]: test udev: [-----------------------
umount: test/tmpfs: no mount point specified.
mknod: test/tmpfs/dev/null: Operation not permitted
unable to create test/tmpfs/dev/null at ./udev-test.pl line 1611.
Failed to set up the environment, skipping the test at ./udev-test.pl line 1731.
autopkgtest [12:45:41]: test udev: -----------------------]
autopkgtest [12:45:44]: test udev: - - - - - - - - - - results - - - - - - - - - -
udev FAIL non-zero exit status 77
rm: cannot remove '/tmp/autopkgtest.ocPFA6/autopkgtest_tmp/test/tmpfs': Device or resource busy
autopkgtest [12:46:22]: ERROR: "rm -rf /tmp/autopkgtest.ocPFA6/udev-artifacts /tmp/autopkgtest.ocPFA6/autopkgtest_tmp" failed with stderr "rm:
|
|\ \
| | |
| | | |
Various test/test-functions fixes/improvements
|
| | |
| | |
| | |
| | |
| | |
| | | |
The `set -e` option is incompatible with a subshell/compound command,
which is followed by || <EXPR>. In such case, the -e option is ignored
in all affected subshells/functions (see man bash(1) for command `set`).
|
| | | |
|