From d899734475f09068dfa410c91e126e1442b0325e Mon Sep 17 00:00:00 2001 From: Colin Walters Date: Tue, 9 Dec 2008 09:15:06 -0500 Subject: Bug 18229: Allow signals Our previous fix went too far towards lockdown; many things rely on signals to work, and there's no really good reason to restrict which signals can be emitted on the bus because we can't tie them to a particular sender. --- test/name-test/run-test-systemserver.sh | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'test/name-test/run-test-systemserver.sh') diff --git a/test/name-test/run-test-systemserver.sh b/test/name-test/run-test-systemserver.sh index fd82326c..34dd6487 100755 --- a/test/name-test/run-test-systemserver.sh +++ b/test/name-test/run-test-systemserver.sh @@ -39,3 +39,12 @@ if ! grep -q 'DBus.Error' echo-error-output.tmp; then echo "=====" exit 1 fi + +echo "running test echo signal" +if ! python ./test-wait-for-echo.py; then + echo "Failed test-wait-for-echo" + exit 1 +fi + + +exit 0 -- cgit