mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-05-27 19:38:14 +02:00
baaab52266
Most nmcli calls from clients/tests don't change the server's state. Hence, they can easily run in parallel. Run tests in parallel. No longer handle one nmcli invocation after the other. Instead, spawn groups of processes in parallel, and track the pending jobs. Only at certain synchronization points we call self.async_wait() to wait for all previous jobs to complete. This reduces the test time on my machine from 7 to 3 seconds. Arguably, that matters less during a full `make check -j 8`, because the entire set of tests anyway takes longer than 7 seconds. So when running the entire test suite, the machine is kept busy anyway. It matters however for manual invocations.
39 lines
764 B
Text
39 lines
764 B
Text
location: clients/tests/test-client.py:674:test_002()/5
|
|
cmd: $NMCLI
|
|
lang: C
|
|
returncode: 0
|
|
stdout: 621 bytes
|
|
>>>
|
|
eth0: unavailable
|
|
"eth0"
|
|
ethernet (virtual), 72:41:AB:90:41:5D, hw
|
|
|
|
eth1: unavailable
|
|
"eth1"
|
|
ethernet (virtual), 1F:E6:D1:E6:1D:53, hw
|
|
|
|
wlan0: unavailable
|
|
"wlan0"
|
|
wifi (virtual), 5A:88:5E:B6:90:40, hw
|
|
|
|
wlan1: unavailable
|
|
"wlan1"
|
|
wifi (virtual), 7C:D4:69:31:67:0B, hw
|
|
|
|
wlan1: unavailable
|
|
"wlan1"
|
|
wifi (virtual), 41:21:6B:F3:C9:4A, hw
|
|
|
|
DNS configuration:
|
|
servers: 1.2.3.4 5.6.7.8
|
|
|
|
Use "nmcli device show" to get complete information about known devices and
|
|
"nmcli connection show" to get an overview on active connection profiles.
|
|
|
|
Consult nmcli(1) and nmcli-examples(5) manual pages for complete usage details.
|
|
|
|
<<<
|
|
stderr: 0 bytes
|
|
>>>
|
|
|
|
<<<
|