[
https://issues.apache.org/jira/browse/HADOOP-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613953#action_12613953
]
Hadoop QA commented on HADOOP-3743:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12386135/patch-3743.txt
against trunk revision 677127.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 10 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2872/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2872/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2872/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2872/console
This message is automatically generated.
> -libjars, -files and -archives options do not work with 0.18
> ------------------------------------------------------------
>
> Key: HADOOP-3743
> URL: https://issues.apache.org/jira/browse/HADOOP-3743
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.17.0
> Reporter: Mahadev konar
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.18.0
>
> Attachments: patch-3743.txt, patch-3743.txt, patch-3743.txt,
> patch-3743.txt
>
>
> I am not sure how to get -libjars and -files working with 0.18. I tried all
> the options but cannot get it runnning. I am filing this as a blocker until
> we find out that its not broken. -- in that case we need to update the docs
> with an example to say how it works.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
