From: Frantisek Sumsal Date: Thu, 28 Mar 2024 14:20:22 +0000 (+0100) Subject: test: check if sd-executor doesn't complain during (de)serializing X-Git-Tag: v256-rc1~338^2~2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c956bf31f8e58e23740c2b58a779570eca49591e;p=thirdparty%2Fsystemd.git test: check if sd-executor doesn't complain during (de)serializing This was usually caught by "accident" by other tests that parse output of commands executed by sd-executor, so let's have an explicit check for this. --- diff --git a/test/units/end.sh b/test/units/end.sh index 4c6c0afa0e9..5e2943758a1 100755 --- a/test/units/end.sh +++ b/test/units/end.sh @@ -9,5 +9,9 @@ set -o pipefail # Here, the redundant '[ ]' in the pattern is required in order not to match the logged command itself. (! journalctl -q -o short-monotonic --grep 'Warning: cannot close sd-bus connection[ ].*after fork' >>/failed) +# Check if sd-executor doesn't complain about not being able to (de)serialize stuff +(! journalctl -q -o short-monotonic --grep "[F]ailed to parse serialized line" >>/failed) +(! journalctl -q -o short-monotonic --grep "[F]ailed to (de)?serialize \w+" >>/failed) + systemctl poweroff --no-block exit 0