[ 
https://issues.apache.org/jira/browse/HADOOP-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604406#action_12604406
 ] 

Hadoop QA commented on HADOOP-3533:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12383879/compat.patch
  against trunk revision 666620.

    +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 appears to have generated 1 warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    -1 findbugs.  The patch appears to cause Findbugs to fail.

    +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 failed contrib unit tests.

Test results: 
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2644/testReport/
Checkstyle results: 
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2644/artifact/trunk/build/test/checkstyle-errors.html
Console output: 
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2644/console

This message is automatically generated.

> The api to JobTracker and TaskTracker have changed incompatibly
> ---------------------------------------------------------------
>
>                 Key: HADOOP-3533
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3533
>             Project: Hadoop Core
>          Issue Type: Bug
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>            Priority: Blocker
>             Fix For: 0.18.0
>
>         Attachments: compat.patch
>
>
> The JobTracker and TaskTracker classes are currently both public, and while 
> working on HADOOP-3532, I discovered that their API's have been changed 
> incompatibly. I believe the best course of action is to make their visibility 
> package private.
> Thoughts?

-- 
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