hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5736) Update CapacityScheduler documentation to reflect latest changes
Date Tue, 05 May 2009 08:30:30 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705953#action_12705953

Hemanth Yamijala commented on HADOOP-5736:

Results of test-patch:

     [exec] -1 overall.
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]     -1 tests included.  The patch doesn't appear to include any new or modified
     [exec]                         Please justify why no tests are needed for this patch.
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
     [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
     [exec]     -1 release audit.  The applied patch generated 474 release audit warnings
(more than the trunk's current 473 warnings).

There are no tests because this is a documentation patch.
The release audit warning seems to be in the generated documentation files. Hence, I think
it can be ignored.

> Update CapacityScheduler documentation to reflect latest changes
> ----------------------------------------------------------------
>                 Key: HADOOP-5736
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5736
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/capacity-sched
>            Reporter: Sreekanth Ramakrishnan
>            Assignee: Sreekanth Ramakrishnan
>         Attachments: documentation-20.patch, documentation.patch
> Update capacity scheduler documentation to reflect the latest changes.

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

View raw message