Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net/http: unit test failure #3494

Closed
alberts opened this issue Apr 7, 2012 · 12 comments
Closed

net/http: unit test failure #3494

alberts opened this issue Apr 7, 2012 · 12 comments

Comments

@alberts
Copy link
Contributor

alberts commented Apr 7, 2012

What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.

run the net/http test a few hundred times

What do you see instead?

--- FAIL: TestIdentityResponse (0.00 seconds)
serve_test.go:332: for http://127.0.0.1:38967/?te= expected res.ContentLength of 3; got
-1
serve_test.go:335: for http://127.0.0.1:38967/?te= expected Content-Length header of
"3"; got ""
serve_test.go:339: for http://127.0.0.1:38967/?te= expected len(res.TransferEncoding) of
0; got 1 ([chunked])
serve_test.go:332: for http://127.0.0.1:38967/?te=identity expected res.ContentLength of
3; got -1
serve_test.go:335: for http://127.0.0.1:38967/?te=identity expected Content-Length
header of "3"; got ""
serve_test.go:339: for http://127.0.0.1:38967/?te=identity expected
len(res.TransferEncoding) of 0; got 1 ([chunked])

Which compiler are you using (5g, 6g, 8g, gccgo)?

6g

Which operating system are you using?

linux

Which version are you using?  (run 'go version')

go version weekly.2012-03-27 +d9e4f47ae341
@alberts
Copy link
Contributor Author

alberts commented Apr 7, 2012

Comment 1:

Another run also turned up a failure:
--- FAIL: TestSetsRemoteAddr-9 (0.00 seconds)
serve_test.go:448: Expected local addr; got "req=3"

@bradfitz
Copy link
Contributor

Comment 2:

I looked at the test, expecting to find a race, but I don't see anything suspicious.
Tips welcome.

@alberts
Copy link
Contributor Author

alberts commented Apr 11, 2012

Comment 3:

Another one:
--- FAIL: TestFSRedirect-36 (0.00 seconds)
fs_test.go:118: redirect from /test/index.html: got /test/index.html, want /test/
fs_test.go:118: redirect from /test/testdata: got /test/testdata, want /test/testdata/
fs_test.go:118: redirect from /test/testdata/file/: got /test/testdata/file/, want
/test/testdata/file
go version weekly.2012-03-27 +1b2b113a2d66
doesn't seem as if anything in this area has been touched between this change and tip.
We have a builder running most of the Go test suite 24/7 now with random values of
GOMAXPROCS, which is why these are turning up.

@rsc
Copy link
Contributor

rsc commented Apr 11, 2012

Comment 4:

I expect this to be a client bug, that the client is misinterpreting
responses somehow.
Or maybe the server is mixing responses.

@rsc
Copy link
Contributor

rsc commented Apr 11, 2012

Comment 5:

I expect this to be a client bug, that the client is misinterpreting
responses somehow.
Or maybe the server is mixing responses.

@alberts
Copy link
Contributor Author

alberts commented Apr 12, 2012

Comment 6:

A last example, in case it helps:
--- FAIL: TestServeIndexHtml-38 (0.00 seconds)
fs_test.go:322: for path "/testdata/" got "404 page not found\n", want "index.html says
hello\n"
fs_test.go:322: for path "/testdata/index.html" got "404 page not found\n", want
"index.html says hello\n"

@ianlancetaylor
Copy link
Contributor

Comment 7:

Labels changed: added priority-asap, removed priority-triage.

@alberts
Copy link
Contributor Author

alberts commented Apr 30, 2012

Comment 8:

They're quite rare at tip now, but I see about one every 100 runs.
--- FAIL: TestRoundTripGzip-52 (0.00 seconds)
transport_test.go:480: 0. body = ""; want "test response body"
transport_test.go:480: 1. body = ""; want "test response body"
transport_test.go:486: 1. Content-Encoding = ""; want "foo"
transport_test.go:467: 2. gzip NewReader: EOF

@bradfitz
Copy link
Contributor

Comment 9:

Labels changed: removed priority-asap.

Owner changed to @bradfitz.

Status changed to Accepted.

@bradfitz
Copy link
Contributor

Comment 10:

Has this been seen recently?

@alberts
Copy link
Contributor Author

alberts commented Jul 30, 2012

Comment 11:

Haven't seen any of these for a while. Only issue #3793.

@bradfitz
Copy link
Contributor

bradfitz commented Aug 7, 2012

Comment 12:

Closing for now.  Please reopen if this is seen again.

Status changed to Invalid.

@alberts alberts added the invalid label Aug 7, 2012
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants