6 Commits

Author	SHA1	Message	Date
Frantisek Sumsal	53008d0714	test: drop unnecessary || : ... since we use `set +e` in the cleanup handler.	2022-06-26 22:06:02 +02:00
Frantisek Sumsal	71cde065b5	test: make TEST-21-DFUZZER work in containers ... by avoiding fuzzing networkd and timesyncd when running in a container.	2022-06-26 22:06:02 +02:00
Frantisek Sumsal	56e8ee55d5	test: make the shutdown routine a bit more "robust" ... Replace the call to the `end.service` with `systemctl poweroff`, since it seems to cause issues no matter what `--job-mode=` is used: ``` [ 129.070993] testsuite-21.sh[380]: ++ systemctl start --job-mode=flush end.service [ 129.154985] testsuite-21.sh[912]: Failed to start end.service: Transaction for end.service/start is destructive (sysinit.target has 'stop' job queued, but 'start' is included in transaction). [ 129.159636] testsuite-21.sh[912]: See system logs and 'systemctl status end.service' for details. ``` Also, add a "safety net" which bypasses the manager and does the poweroff directly, since sometimes the D-Bus call performed by `systemctl` might timeout (as the manager might be still processing data from the fuzzing): ``` [ 115.776778] sh[894]: + systemctl poweroff --no-block [ 166.164242] testsuite-21.sh[893]: Failed to start transient service unit: Connection timed out [ 166.269289] sh[894]: Call to PowerOff failed: Connection timed out ```	2022-06-21 12:11:43 +02:00
Frantisek Sumsal	5309b56505	test: drop the at_exit() coredump check ... since we don't truncate the journal anymore.	2022-06-21 10:13:48 +02:00
Frantisek Sumsal	d3eb4159c9	test: make dfuzzer less verbose ... Otherwise it oversaturates the journal, which in some cases can't keep up with the load of messages (due to the performance penalty caused by sanitizers), and gets killed by a watchdog.	2022-06-21 10:04:03 +02:00
Frantisek Sumsal	354b3364aa	test: fuzz our dbus interfaces with dfuzzer	2022-06-19 16:22:35 +02:00