summaryrefslogtreecommitdiff
path: root/clients/tests/test-client.check-on-disk/test_002-012.expected
diff options
context:
space:
mode:
authorThomas Haller <thaller@redhat.com>2018-06-11 16:36:47 +0200
committerThomas Haller <thaller@redhat.com>2018-06-11 19:30:50 +0200
commitee4655d168023dec9af26a26c2d7c43331c6ee60 (patch)
tree8c5d878900a22781b89e5f27016300f35eeff467 /clients/tests/test-client.check-on-disk/test_002-012.expected
parent3044caa07a643188e296ce4fffb8f1c2240fa583 (diff)
downloadNetworkManager-ee4655d168023dec9af26a26c2d7c43331c6ee60.tar.gz
clients/tests: extend tests to gracefully handle unstable output
Commands that fail with G_DEBUG=fatal-warnings produce unstable output like (process:10743): GLib-CRITICAL **: 16:29:13.635: g_ptr_array_add: assertion 'rarray' failed To workaround that, add a new option for marking the output as unstable. An alternative might be to extend the replace_stdout, replace_stderr arguments to support more powerful matching, like by specifying regular expression for replacing. However, it's just too complicated. Add a simpler workaround by passing _UNSTABLE_OUTPUT.
Diffstat (limited to 'clients/tests/test-client.check-on-disk/test_002-012.expected')
-rw-r--r--clients/tests/test-client.check-on-disk/test_002-012.expected2
1 files changed, 1 insertions, 1 deletions
diff --git a/clients/tests/test-client.check-on-disk/test_002-012.expected b/clients/tests/test-client.check-on-disk/test_002-012.expected
index e59eb3155b..1a068a14ba 100644
--- a/clients/tests/test-client.check-on-disk/test_002-012.expected
+++ b/clients/tests/test-client.check-on-disk/test_002-012.expected
@@ -1,4 +1,4 @@
-location: clients/tests/test-client.py:702:test_002()/12
+location: clients/tests/test-client.py:710:test_002()/12
cmd: $NMCLI -f AP -mode multiline -t d show wlan0
lang: pl_PL.UTF-8
returncode: 0