[ 
https://issues.apache.org/jira/browse/NUTCH-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ciuffetti reopened NUTCH-2059:
------------------------------------

Reopening as build 
https://builds.apache.org/view/All/job/Nutch-trunk/3192/consoleFull failed with 
the same sporadic error.

Looking at the builds that failed, the test (which normally takes about 3s to 
run) fails after more than 60s

{code}
https://builds.apache.org/view/All/job/Nutch-trunk/3192/consoleFull
Started by timer
Building remotely on jenkins-ubuntu-1404-4gb-302 (jenkins-cloud-4GB cloud-slave 
Ubuntu ubuntu) in workspace /jenkins/workspace/Nutch-trunk
Cleaning local Directory trunk
Checking out http://svn.apache.org/repos/asf/nutch/trunk at revision 
'2015-07-05T04:01:16.935 +0000'
    [junit] Tests run: 7, Failures: 0, Errors: 1, Time elapsed: 63.093 sec
    [junit] Test org.apache.nutch.protocol.httpclient.TestProtocolHttpClient 
FAILED
{code}

{code}
https://builds.apache.org/view/All/job/Nutch-trunk/3189/consoleFull
Started by an SCM change
Building remotely on H11 (Ubuntu ubuntu) in workspace 
/home/jenkins/jenkins-slave/workspace/Nutch-trunk
Cleaning local Directory trunk
Checking out http://svn.apache.org/repos/asf/nutch/trunk at revision 
'2015-07-04T08:08:16.100 +0000'
    [junit] Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
64.156 sec
    [junit] Test org.apache.nutch.protocol.httpclient.TestProtocolHttpClient 
FAILED
{code}

If you look at the console log of the test, you will see  that it echos the 
httpclient connection params

{code}
2015-07-05 09:18:07,127 INFO  httpclient.Http (HttpBase.java:logConf(445)) - 
http.proxy.host = null
2015-07-05 09:18:07,127 INFO  httpclient.Http (HttpBase.java:logConf(446)) - 
http.proxy.port = 8080
2015-07-05 09:18:07,128 INFO  httpclient.Http (HttpBase.java:logConf(447)) - 
http.proxy.exception.list = false
2015-07-05 09:18:07,128 INFO  httpclient.Http (HttpBase.java:logConf(448)) - 
http.timeout = 60000
2015-07-05 09:18:07,128 INFO  httpclient.Http (HttpBase.java:logConf(449)) - 
http.content.limit = 65536
2015-07-05 09:18:07,129 INFO  httpclient.Http (HttpBase.java:logConf(450)) - 
http.agent = Nutch-Test/Nutch-1.11-SNAPSHOT (Nutch protocol-httpclient test)
2015-07-05 09:18:07,129 INFO  httpclient.Http (HttpBase.java:logConf(451)) - 
http.accept.language = en-us,en-gb,en;q=0.7,*;q=0.3
2015-07-05 09:18:07,129 INFO  httpclient.Http (HttpBase.java:logConf(452)) - 
http.accept = text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
{code}

...and the http connect timeout is set to 60.  So it looks like a timeout is 
occurring during th fialed test.  On which test it is still uncertain as the 
Jenkins console logs are not accessible.

Would it be possible for a Jenkins admin to provide a copy of the test output 
file?

Building remotely on jenkins-ubuntu-1404-4gb-302 (jenkins-cloud-4GB cloud-slave 
Ubuntu ubuntu) in workspace /jenkins/workspace/Nutch-trunk

the file Im looking for is...

/jenkins/workspace/Nutch-trunk/trunk/build/test/build/protocol-httpclient/test/TEST-org.apache.nutch.protocol.httpclient.TestProtocolHttpClient.txt

Another tack Im taking is to revive the httpclient upgrade in NUTCH-1086 which 
never got to the PR stage.  But its giving me some compiler warnings and its 
own unit test failure that would have to be addressed.

> protocol-httpclient, protocol-http unit test errors on Jenkins
> --------------------------------------------------------------
>
>                 Key: NUTCH-2059
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2059
>             Project: Nutch
>          Issue Type: Bug
>          Components: fetcher
>            Reporter: Peter Ciuffetti
>            Assignee: Chris A. Mattmann
>             Fix For: 1.11
>
>
> This is an occasional error on the build of the Nutch trunk visible in 
> Jenkins builds.  It happens on either protocol-http or protocol-httpclient, 
> which can be running at the same time given the multi-threaded test setup.
> {code}
> [junit] Running org.apache.nutch.protocol.httpclient.TestProtocolHttpClient
> [junit] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.377 
> sec
> [junit] Test org.apache.nutch.protocol.http.TestProtocolHttp FAILED
> {code}
> Evidence of failure on Jenkins go back to
> Failed > Console Output  #3154        Jun 8, 2015 4:00:00 AM
> https://builds.apache.org/view/All/job/Nutch-trunk/3154/consoleFull
> And are repeated at...
> https://builds.apache.org/view/All/job/Nutch-trunk/3190/console
> https://builds.apache.org/view/All/job/Nutch-trunk/3189/console
> Some possibly related tickets
> NUTCH-1836 Timeouts in protocol-httpclient when crawling same host with >2 
> threads 
> NUTCH-1086 Rewrite protocol-httpclient
> The unit tests are not failing for me on my sandbox, but there are some 
> exceptions being output to the log related to headers being sent on JSP pages 
> after the response writer is invoked.
> {code}
> java.lang.IllegalStateException: STREAM
>         at org.mortbay.jetty.Response.getWriter(Response.java:616)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to