# HG changeset patch
# User mas01cr
# Date 1191424325 0
# Node ID 6066d75a6d39479f5af8254ca6865c6cabd24fb5
# Parent  03564e8988a2da2fe5a30d8d2123a5cf79f8dcba
Rename expect_server_failure() to expect_client_failure().

Not that it's that much of a better name but at least no longer implies
that we expect the server to fall over.  What we expect is a server
error code, and maybe eventually a client detection of that with
friendly reporting to the user.  Ha ha.

diff -r 03564e8988a2 -r 6066d75a6d39 tests/0015/run-test.sh
--- a/tests/0015/run-test.sh	Wed Oct 03 14:13:05 2007 +0000
+++ b/tests/0015/run-test.sh	Wed Oct 03 15:12:05 2007 +0000
@@ -27,8 +27,8 @@
 
 check_server $!
 
-expect_server_failure ${AUDIODB} -c localhost:10015 -S -d /dev/null
-expect_server_failure ${AUDIODB} -c localhost:10015 -S -d /tmp/foo-does-not-exist
+expect_client_failure ${AUDIODB} -c localhost:10015 -S -d /dev/null
+expect_client_failure ${AUDIODB} -c localhost:10015 -S -d /tmp/foo-does-not-exist
 
 check_server $!
 
diff -r 03564e8988a2 -r 6066d75a6d39 tests/test-utils.sh
--- a/tests/test-utils.sh	Wed Oct 03 14:13:05 2007 +0000
+++ b/tests/test-utils.sh	Wed Oct 03 15:12:05 2007 +0000
@@ -67,7 +67,7 @@
   grep ${AUDIODB} /proc/$1/cmdline > /dev/null
 }
 
-expect_server_failure() {
+expect_client_failure() {
   # FIXME: work out whether and how the client should report server
   # errors.  At present, the client exits with a zero exit code.
   "$@"