Thomas Haller 27c0d9d8b7 clients/tests: comment return code by signal in test output ... Otherwise, we just see "returncode: -11", which isn't very clear. By default, our test nmcli invocations should never exit by a signal. Usually, when we encounter a signal, it indicates to a bug and a crash during the test. Print more information about the exit code. returncode: -11 (SIGNAL SIGSEGV)		2020-03-23 13:30:13 +01:00
..
cli	cli: support setting removal	2020-03-23 11:42:57 +01:00
cloud-setup	shared/trivial: rename time related functions to use "nsec"/"msec" abbreviation instead of "ns"/"ms"	2020-02-10 19:11:50 +01:00
common	libnm-core: slightly improve sriov setting documentation	2020-03-23 11:42:57 +01:00
tests	clients/tests: comment return code by signal in test output	2020-03-23 13:30:13 +01:00
tui	all: use nm_clear_pointer() instead of g_clear_pointer()	2020-03-23 11:22:38 +01:00
meson.build	nm-online: use nmc_client_new_async() instead of nm_client_new_async()	2019-12-10 09:17:17 +01:00
nm-online.c	all: use nm_clear_pointer() instead of g_clear_pointer()	2020-03-23 11:22:38 +01:00