5 commits

Author	SHA1	Message	Date
Lennart Poettering	ea441dbd9d	ci: test new --graceful= switch of varlinkctl	2024-06-20 18:20:09 +02:00
Lennart Poettering	aa413d5fc6	ci: add superficial --quiet testcase	2024-06-13 11:31:44 +02:00
Lennart Poettering	e1ef88e56e	test: add test for new varlinkctl features	2024-06-13 09:37:15 +02:00
Lennart Poettering	f5faf4ec5b	varlinkctl: when operating in --more mode, fail correcly on Varlink method error ... In varlink.c we generally do not make failing callback functions fatal, since that should be up to the app. Hence, in case of varlinkctl (where we want failures to be fatal), make sure to propagate the error back explicitly. Before this change a failing call to "varlinkctl --more call …" would result in a zero exit code. With this it will correctly exit with a non-zero exit code.	2024-05-22 22:08:28 +02:00
Daan De Meyer	7a321b5a21	test: Rename testsuite-XX units to match test name ... Having these named differently than the test itself mostly creates unecessary confusion and makes writing logic against the tests harder so let's rename the testsuite-xx units and scripts to just use the test name itself.	2024-05-14 12:43:28 +02:00

Renamed from test/units/testsuite-74.varlinkctl.sh (Browse further)