[ 
https://issues.apache.org/jira/browse/HADOOP-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545132
 ] 

Hadoop QA commented on HADOOP-2272:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12370132/HADOOP-2272-1.patch
against trunk revision r597725.

    @author +1.  The patch does not contain any @author tags.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new compiler warnings.

    findbugs -1.  The patch appears to introduce  new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests -1.  The patch failed contrib unit tests.

Test results: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1150/testReport/
Findbugs warnings: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1150/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1150/artifact/trunk/build/test/checkstyle-errors.html
Console output: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1150/console

This message is automatically generated.

> findbugs currently fails due to hadoop-streaming having moved
> -------------------------------------------------------------
>
>                 Key: HADOOP-2272
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2272
>             Project: Hadoop
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.15.0
>            Reporter: Adrian Woodhead
>         Attachments: HADOOP-2272-1.patch
>
>
> If you do a fresh checkout of the trunk and try run findbugs you get the 
> following error:
> findbugs:
>  [findbugs] Running FindBugs...
>  [findbugs] Exception in thread "main" java.util.zip.ZipException: Error 
> opening /tmp/x/trunk/build/hadoop-0.16.0-dev-streaming.jar
>  [findbugs]     at 
> edu.umd.cs.findbugs.classfile.impl.ZipFileCodeBase.<init>(ZipFileCodeBase.java:61)
>  [findbugs]     at 
> edu.umd.cs.findbugs.classfile.impl.ClassFactory.createFilesystemCodeBase(ClassFactory.java:96)
>  [findbugs]     at 
> edu.umd.cs.findbugs.classfile.impl.FilesystemCodeBaseLocator.openCodeBase(FilesystemCodeBaseLocator.java:63)
>  [findbugs]     at 
> edu.umd.cs.findbugs.classfile.impl.ClassPathBuilder.processWorkList(ClassPathBuilder.java:381)
>  [findbugs]     at 
> edu.umd.cs.findbugs.classfile.impl.ClassPathBuilder.build(ClassPathBuilder.java:192)
>  [findbugs]     at 
> edu.umd.cs.findbugs.FindBugs2.buildClassPath(FindBugs2.java:432)
>  [findbugs]     at edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:160)
>  [findbugs]     at edu.umd.cs.findbugs.FindBugs.runMain(FindBugs.java:1521)
>  [findbugs]     at edu.umd.cs.findbugs.FindBugs2.main(FindBugs2.java:731)
>  [findbugs] Output saved to 
> /tmp/x/trunk/build/test/findbugs/hadoop-findbugs-report.xml
>      [xslt] Processing 
> /tmp/x/trunk/build/test/findbugs/hadoop-findbugs-report.xml to 
> /tmp/x/trunk/build/test/findbugs/hadoop-findbugs-report.html
>      [xslt] Loading stylesheet /opt/java/findbugs/src/xsl/default.xsl
>      [xslt] : Error! Premature end of file.
>      [xslt] : Error! 
> com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Premature end 
> of file.
>      [xslt] Failed to process 
> /tmp/x/trunk/build/test/findbugs/hadoop-findbugs-report.xml
> BUILD FAILED
> /tmp/x/trunk/build.xml:599: javax.xml.transform.TransformerException: 
> javax.xml.transform.TransformerException: 
> com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Premature end 
> of file.
> ----
> This is because 
> build/hadoop-0.16.0-dev-streaming.jar 
> is the wrong location, it should be 
> build/contrib/streaming/hadoop-0.16.0-dev-streaming.jar 
> I think this also explains why Hudson is currently giving a -1 to all new 
> patches as findbugs is failing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to