summaryrefslogtreecommitdiff
path: root/clients/tests/test-client.check-on-disk/test_003-014.expected
diff options
context:
space:
mode:
authorThomas Haller <thaller@redhat.com>2018-05-15 12:06:08 +0200
committerThomas Haller <thaller@redhat.com>2018-05-24 16:40:17 +0200
commit7ae5fb7ec61f7215b3d609f656403b432ca20028 (patch)
treee09536a1abb10bf660160e208d64ecdf304218fd /clients/tests/test-client.check-on-disk/test_003-014.expected
parentd5e25a4324e4e8a57b0411d8daecdd3c13df9cfb (diff)
downloadNetworkManager-7ae5fb7ec61f7215b3d609f656403b432ca20028.tar.gz
clients/tests: test nmcli output for multiple activation of same profile
Activate the same profile on two devices. Arguably, real NetworkManager (currently) does not allow that. But the D-Bus API is fine with having multiple ActiveConnections for one SettingsConnection. So, also the client should do something sensible. Also, later we will add wildcard support to NetworkManager, which means that a profile can be active multiple times (simultaneously).
Diffstat (limited to 'clients/tests/test-client.check-on-disk/test_003-014.expected')
-rw-r--r--clients/tests/test-client.check-on-disk/test_003-014.expected2
1 files changed, 1 insertions, 1 deletions
diff --git a/clients/tests/test-client.check-on-disk/test_003-014.expected b/clients/tests/test-client.check-on-disk/test_003-014.expected
index bcbe7938c7..c4ddaecd94 100644
--- a/clients/tests/test-client.check-on-disk/test_003-014.expected
+++ b/clients/tests/test-client.check-on-disk/test_003-014.expected
@@ -1,4 +1,4 @@
-location: clients/tests/test-client.py:607:test_003()/14
+location: clients/tests/test-client.py:609:test_003()/14
cmd: $NMCLI --complete-args -f ALL c s ''
lang: de_DE.utf8
returncode: 0