[ 
https://issues.apache.org/jira/browse/MAPREDUCE-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245694#comment-13245694
 ] 

Hadoop QA commented on MAPREDUCE-4020:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12521189/MAPREDUCE-4020-branch-23.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 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 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) 
warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    -1 core tests.  The patch failed these unit tests:
                  org.apache.hadoop.mapreduce.v2.TestMiniMRProxyUser
                  org.apache.hadoop.mapreduce.v2.TestSpeculativeExecution
                  org.apache.hadoop.mapred.TestSpecialCharactersInOutputPath
                  org.apache.hadoop.mapreduce.v2.TestRMNMInfo
                  org.apache.hadoop.mapred.TestReduceFetchFromPartialMem
                  org.apache.hadoop.mapred.TestLazyOutput
                  org.apache.hadoop.mapreduce.TestChild
                  org.apache.hadoop.mapred.TestReduceFetch
                  org.apache.hadoop.mapred.TestMiniMRBringup
                  org.apache.hadoop.mapred.TestMiniMRClientCluster
                  org.apache.hadoop.mapreduce.lib.output.TestJobOutputCommitter
                  org.apache.hadoop.mapreduce.v2.TestMROldApiJobs
                  org.apache.hadoop.mapreduce.v2.TestNonExistentJob
                  org.apache.hadoop.mapred.TestMiniMRChildTask
                  org.apache.hadoop.mapred.TestJobCounters
                  org.apache.hadoop.mapreduce.v2.TestUberAM
                  org.apache.hadoop.conf.TestNoDefaultsJobConf
                  org.apache.hadoop.mapred.TestJobSysDirWithDFS
                  org.apache.hadoop.mapreduce.v2.TestMRJobs
                  org.apache.hadoop.mapred.TestClientRedirect
                  org.apache.hadoop.mapred.TestJobCleanup
                  org.apache.hadoop.mapreduce.TestMapReduceLazyOutput

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2136//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2136//console

This message is automatically generated.
                
> Web services returns incorrect JSON for deep queue tree
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-4020
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4020
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, webapps
>    Affects Versions: 0.23.1
>            Reporter: Jason Lowe
>            Assignee: Anupam Seth
>         Attachments: MAPREDUCE-4020-branch-23.patch, 
> MAPREDUCE-4020-branch-23.patch, MAPREDUCE-4020-branch-23.patch, 
> MAPREDUCE-4020-branch-23.patch, MAPREDUCE-4020-branch-23.patch, 
> MAPREDUCE-4020-branch-23.patch, testcase.patch
>
>
> When the capacity scheduler is configured for more than two levels of queues, 
> the web services API returns incorrect JSON for the subQueues field of some 
> parent queues.  The "subQueues" field for parent queues should always be an 
> array, but sometimes the field appears multiple times for a queue and as what 
> looks like a CapacityQueueInfo object instead of an array.  Besides the 
> sometimes-an-array-sometimes-not problem, parsing the result into a JSON 
> object causes all but the last "subQueues" field to be discarded since they 
> are overwritten by subsequent fields with the same name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to