http.TestClient and TestRedirect FAIL: Get http://www.google.com/robots.txt: unexpected EOF

[gopherbot]

by lcgong:

What steps will reproduce the problem?
1. ./all.bash
2.
3.

What is the expected output? What do you see instead?


--- FAIL: http.TestClient
    Get http://www.google.com/robots.txt: read
tcp:10.112.1.82:54219->216.239.61.104:80: connection reset by peer
--- FAIL: http.TestRedirect
    Get http://codesearch.google.com/: unexpected EOF
FAIL


What is your $GOOS?  $GOARCH?
linux/386

Which revision are you sync'ed to?  (hg log -l 1)

3973:aa68d0be67fa

Please provide any additional information below.

[agl]

Comment 1:

This is typically caused by a firewall. Note, however, that everything is already 
built and installed at this stage. You can also add http to the NOTEST list in 
src/pkg/Makefile to skip this test.

Status changed to Accepted.

[gopherbot]

Comment 2 by lcgong:

done
thanks

[gopherbot]

Comment 3 by weilyyoung:

I met the similar issue. I know everything has been successfully built and installed. 
But I wonder what is the root cause of the "unexpected EOF"? Thanks.
Here's my output:
--- FAIL: http.TestClient
    Get http://www.google.com/robots.txt: unexpected EOF
--- FAIL: http.TestRedirect
    Get http://codesearch.google.com/: unexpected EOF

[gopherbot]

Comment 4 by michael.jones:

weilyyoung, do you have a firewall enabled on your computer that blocks these http 
requests? As was answered above, if you disable this you should be OK or if you can't 
disable it, then disable the test as explained. I disabled my OS X firewall and the
tests 
passed.

[gopherbot]

Comment 6 by weilyyoung:

Hi, Michael. I'm running ubuntu 9.10 and all firewalls (iptables) are disabled (double 
checked with iptables -L -n). 
lcgong's issue is "connection reset by peer" which should be related to the firewall. 
But why "unexpected EOF" is related to firewall? I use firefox to get the URL, it works 
well. So may be some issue in this test code.

[gopherbot]

Comment 7 by weilyyoung:

I attached 2 capture files. The "httpTestClientFail.pcap" contains the packet sequence 
when trying to get the robot.txt file from google. It seems the connection is 
incorrectly FIN and RST by the server. 
But in "googleRobot.pcap" file, it contains the packets when I tried using FireFox for 
http://www.google.com/robot.txt. It seems everything is correct. 
Not sure why google's server doesn't allow the HTTP GET from "go client".

Attachments:

1. httpTestClientFail.pcap (1275 bytes)
2. googleRobot.pcap (2898 bytes)

[gopherbot]

Comment 8 by ptw007:

Just a little more information to pass along. It's not my work, it's others and I am
just the mediator.  I now how to fit things together but I can't create the technology

[gopherbot]

Comment 9 by subhrangshus:

I am having a problem with the printer test:
--- FAIL: printer.Test
How can I switch off this part in the Makefile.
BTW, if has everything been installed if I have reached rhis far ? Then I won't 
bother.

[gopherbot]

Comment 10 by subhrangshus:

Went past the printer error by including it in the NOTEST list.
Now I am getting the following error:
--- FAIL: tar.TestReader
        test 0: Unexpected error: open testdata/gnu.tar: error 530
        test 1: Unexpected error: open testdata/star.tar: error 530
        test 2: Unexpected error: open testdata/v7.tar: error 530
--- FAIL: tar.TestPartialRead
        Unexpected error: open testdata/gnu.tar: error 530
--- FAIL: tar.TestWriter
        test 0: Unexpected error: open testdata/writer.tar: error 530
        test 1: Unexpected error: open testdata/writer-big.tar: error 530
FAIL
make[1]: *** [test] Error 1
make[1]: Leaving directory `/go/src/pkg/archive/tar'
make: *** [archive/tar.test] Error 2

[gopherbot]

Comment 11 by nathanollerenshaw:

google seems to block certain IPs/networks from accessing it's website. I think its a
bad idea to rely on network connectivity to build, anyway. My network at work doesn't
have any route to the internet, for example.
Maybe, start a local server, and talk to that.

[rsc]

Comment 12:

Issue #177 has been merged into this issue.

[rsc]

Comment 14:

Issue #199 has been merged into this issue.

[gopherbot]

Comment 15 by pmetzger:

Just encountered this while building on OS X. Merely adding http to NOTEST caused
another network related test to fail. It seems that it would be better if the build
infrastructure didn't assume that the build machine is on the internet and has no
packet filter on.

[gopherbot]

Comment 16 by dujinfang:

not a firewall problem. Last time I run into this problem but can get the url with
curl without problem.

[gopherbot]

Comment 17 by luger.lee:

Does the way to solve it has been found ?