-
Notifications
You must be signed in to change notification settings - Fork 17.5k
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: TestServeFileMimeType failure #4021
Labels
Milestone
Comments
Still seeing this stuff. Here's another one: --- FAIL: TestIdentityResponse-46 (0.00 seconds) serve_test.go:350: for http://127.0.0.1:39895/?te= expected res.ContentLength of 3; got -1 serve_test.go:353: for http://127.0.0.1:39895/?te= expected Content-Length header of "3"; got "" serve_test.go:357: for http://127.0.0.1:39895/?te= expected len(res.TransferEncoding) of 0; got 1 ([chunked]) serve_test.go:350: for http://127.0.0.1:39895/?te=identity expected res.ContentLength of 3; got -1 serve_test.go:353: for http://127.0.0.1:39895/?te=identity expected Content-Length header of "3"; got "" serve_test.go:357: for http://127.0.0.1:39895/?te=identity expected len(res.TransferEncoding) of 0; got 1 ([chunked]) FAIL It helps to disable TestStressSurpriseServerCloses (because it takes a while) and then run: #!/bin/bash set -xe go test -c net/http while true; do GOMAXPROCS=$[ 1 + $[ RANDOM % 1024 ]] ./http.test -test.v done Also, I've found that TestStressSurpriseServerCloses deadlocks from time to time. It seems related to some kind of error condition that arises when the system has too many sockets in the TIME_WAIT state. Running TestStressSurpriseServerCloses in a loop for about 10 to 20 iterations produces this situation. |
Sorry, I didn't realize this was the same issue when I filed the dup issue #4436. If you believe this isn't the same issue, feel free to reopen this one. Status changed to Duplicate. Merged into issue #4436. |
TestStressSurpriseServerCloses hanging (I've never seen that, but could believe it?) is probably related to issue #4191 which has a fix but is waiting on related issue #4434. I think (2) was already fixed by my httptest change http://code.google.com/p/go/source/detail?r=cd3ad880 |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: