[
https://issues.apache.org/jira/browse/NUTCH-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625417#comment-14625417
]
Peter Ciuffetti edited comment on NUTCH-2059 at 7/13/15 9:54 PM:
-----------------------------------------------------------------
...and there's another thing...
The src/plugin/build-plugin.xml does not use the propert file to control format
of the tests. Its hardwired to 'plain'
{code:xml}
<junit printsummary="yes" haltonfailure="no" fork="yes"
errorProperty="tests.failed" failureProperty="tests.failed">
<sysproperty key="test.data" value="${build.test}/data"/>
<sysproperty key="test.input" value="${root}/data"/>
<sysproperty key="javax.xml.parsers.DocumentBuilderFactory"
value="com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl"/>
<classpath refid="test.classpath"/>
<formatter type="plain" />
<batchtest todir="${build.test}" unless="testcase">
<fileset dir="${src.test}"
includes="**/Test*.java" excludes="**/${test.exclude}.java" />
</batchtest>
<batchtest todir="${build.test}" if="testcase">
<fileset dir="${src.test}" includes="**/${testcase}.java"/>
</batchtest>
</junit>
{code}
I've tested
<formatter type="${test.junit.output.format}" />
..with...
ant -Dtest.junit.output.format=xml test-plugins
...and this produces the expected XML
was (Author: peterciuffetti):
...and there's another thing...
The src/plugin/build-plugin.xml does not use the propert file to control format
of the tests. Its hardwired to 'plain'
{code:xml}
<junit printsummary="yes" haltonfailure="no" fork="yes"
errorProperty="tests.failed" failureProperty="tests.failed">
<sysproperty key="test.data" value="${build.test}/data"/>
<sysproperty key="test.input" value="${root}/data"/>
<sysproperty key="javax.xml.parsers.DocumentBuilderFactory"
value="com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl"/>
<classpath refid="test.classpath"/>
<formatter type="plain" />
<batchtest todir="${build.test}" unless="testcase">
<fileset dir="${src.test}"
includes="**/Test*.java" excludes="**/${test.exclude}.java" />
</batchtest>
<batchtest todir="${build.test}" if="testcase">
<fileset dir="${src.test}" includes="**/${testcase}.java"/>
</batchtest>
</junit>
{code}
> 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)
