[
https://issues.apache.org/jira/browse/HADOOP-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606504#action_12606504
]
Hadoop QA commented on HADOOP-3505:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12384282/HADOOP-3505
against trunk revision 669547.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+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 passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2698/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2698/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2698/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2698/console
This message is automatically generated.
> omissions in HOD documentation
> ------------------------------
>
> Key: HADOOP-3505
> URL: https://issues.apache.org/jira/browse/HADOOP-3505
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/hod, documentation
> Reporter: Ari Rabkin
> Assignee: Vinod Kumar Vavilapalli
> Priority: Blocker
> Fix For: 0.18.0
>
> Attachments: HADOOP-3505
>
>
> There's a couple HOD limitations that really trip up the unwary.
> Two I've encountered are that hod can't take relative paths on the command
> line, and that if you pass hod a tarball with a modified /conf, then the
> cluster will fail mysteriously to be initialized.
> I don't see any references to either in the documentation, and it'd be great
> to write this down.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
