From f6d448bc21c3bde3ab39b55664722b40f5801c20 Mon Sep 17 00:00:00 2001
From: Eric Wong <normalperson@yhbt.net>
Date: Fri, 7 Jan 2011 18:05:28 -0800
Subject: redirect unexpected test output to /dev/null

We check the return code anyways, and spewing random binary
data to the terminal with verbosity on is not a good idea.
---
 t/byte-range-common.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 't')

diff --git a/t/byte-range-common.sh b/t/byte-range-common.sh
index b4852a6..ba05864 100644
--- a/t/byte-range-common.sh
+++ b/t/byte-range-common.sh
@@ -55,7 +55,7 @@ t_begin "normal full request matches" && {
 
 t_begin "crazy offset goes over" && {
 	range_insane=-r$(($random_blob_size * 2))-$(($random_blob_size * 4))
-	curl -vsS 2>$err $range_insane $url
+	curl -vsS 2>$err $range_insane $url >/dev/null
 	grep '^< HTTP/1\.[01] 416 ' $err || die "expected 416 error"
 	grep '^< Content-Range: bytes \*/'$random_blob_size $err || \
           die "expected Content-Range: bytes */SIZE"
-- 
cgit v1.2.3-24-ge0c7