From: Brad Fitzpatrick <bradfitz@golang.org>
Date: Wed, 24 Aug 2011 12:09:49 +0000 (+0400)
Subject: http: adjust test threshold for larger suse buffers
X-Git-Tag: weekly.2011-09-01~103
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=fa6d038e9848c529e0ddffad8ba4f21043774f06;p=gostls13.git

http: adjust test threshold for larger suse buffers

My theory is that suse has larger TCP buffer sizes
by default.  I now check over 100MB, rather than over 2MB.
100MB is ~halfway between the 1MB limit and the 200MB
request that's attempted.

R=golang-dev, dsymonds
CC=golang-dev
https://golang.org/cl/4926048
---

diff --git a/src/pkg/http/serve_test.go b/src/pkg/http/serve_test.go
index cfd71d4b4a..08925faa0e 100644
--- a/src/pkg/http/serve_test.go
+++ b/src/pkg/http/serve_test.go
@@ -944,7 +944,7 @@ func TestRequestBodyLimit(t *testing.T) {
 	// the remote side hung up on us before we wrote too much.
 	_, _ = DefaultClient.Do(req)
 
-	if nWritten > limit*2 {
+	if nWritten > limit*100 {
 		t.Errorf("handler restricted the request body to %d bytes, but client managed to write %d",
 			limit, nWritten)
 	}