diff options
| author | Thomas Haller <thaller@redhat.com> | 2018-05-28 14:01:25 +0200 |
|---|---|---|
| committer | Thomas Haller <thaller@redhat.com> | 2018-05-28 16:24:22 +0200 |
| commit | baaab52266961d7b36a627eed5bd48d192c3534c (patch) | |
| tree | 8bf9facee45fdf916c889ebcadbc4a177369228a /clients/tests/test-client.check-on-disk/test_001-002.expected | |
| parent | f0cdd28db3861fd4de8cd16085ca792afaafc8df (diff) | |
| download | NetworkManager-baaab52266961d7b36a627eed5bd48d192c3534c.tar.gz | |
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.
Diffstat (limited to 'clients/tests/test-client.check-on-disk/test_001-002.expected')
| -rw-r--r-- | clients/tests/test-client.check-on-disk/test_001-002.expected | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/clients/tests/test-client.check-on-disk/test_001-002.expected b/clients/tests/test-client.check-on-disk/test_001-002.expected index 8a79af5c93..bcbb86ee12 100644 --- a/clients/tests/test-client.check-on-disk/test_001-002.expected +++ b/clients/tests/test-client.check-on-disk/test_001-002.expected @@ -1,4 +1,4 @@ -location: clients/tests/test-client.py:586:test_001()/2 +location: clients/tests/test-client.py:651:test_001()/2 cmd: $NMCLI lang: pl_PL.UTF-8 returncode: 0 |