Thomas Haller baaab52266 clients/tests: run nmcli commands in parallel ... 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.		2018-05-28 16:24:22 +02:00
..
cli	cli: avoid bogus line seprator in pretty-output	2018-05-25 17:36:47 +02:00
common	all: add stable-id specifier "${DEVICE}"	2018-05-28 14:59:08 +02:00
tests	clients/tests: run nmcli commands in parallel	2018-05-28 16:24:22 +02:00
tui	all: use the elvis operator wherever possible	2018-05-10 14:36:58 +02:00
meson.build	build/meson: use variables for ldflags and linker-script	2018-01-11 12:46:01 +01:00
nm-online.c	all: require glib 2.40	2018-01-18 11:45:36 +01:00