[
https://issues.apache.org/jira/browse/MAPREDUCE-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425587#comment-13425587
]
Hadoop QA commented on MAPREDUCE-4492:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12538511/MAPREDUCE-4492-trunk.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
-1 findbugs. The patch appears to introduce 4 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 passed unit tests in
hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2681//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2681//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2681//console
This message is automatically generated.
> Configuring total queue capacity between 100.5 and 99.5 at perticular level
> is sucessfull
> -----------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4492
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4492
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha
> Reporter: Nishan Shetty
> Assignee: Mayank Bansal
> Priority: Minor
> Fix For: trunk
>
> Attachments: MAPREDUCE-4492-trunk.patch
>
>
> Scenario:
> 1.Configure a,b queues with capacities 40.0 and 60.5 respectively under root
> queue
> 2.Start process
> Observe that process is started sucessfully with configured queue capacity
> though the total capacity is 100.5(40.0+60.5)
--
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
