[
https://issues.apache.org/jira/browse/HADOOP-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636550#action_12636550
]
Hadoop QA commented on HADOOP-4238:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12390904/HADOOP-4238-2.patch
against trunk revision 701273.
+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 Eclipse classpath. The patch retains Eclipse classpath integrity.
-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/3426/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3426/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3426/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3426/console
This message is automatically generated.
> [mapred] Unavailable schedulingInfo in "hadoop list [all]" output should be
> marked "N/A"
> ----------------------------------------------------------------------------------------
>
> Key: HADOOP-4238
> URL: https://issues.apache.org/jira/browse/HADOOP-4238
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.19.0
> Reporter: Vinod K V
> Assignee: Sreekanth Ramakrishnan
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: HADOOP-4238-1.patch, HADOOP-4238-2.patch
>
>
> When schedulingInfo is not available for a job, "hadoop list [all]" doesn't
> print anything. This, combined with the fact that the columns are not aligned
> properly, makes it difficult to comprehend the output.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
