[
https://issues.apache.org/jira/browse/TEZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280770#comment-14280770
]
Hadoop QA commented on TEZ-1941:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12692817/TEZ-1941.2.txt
against master revision ea46f45.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 5 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:red}-1 findbugs{color}. The patch appears to introduce 64 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/48//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/48//artifact/patchprocess/newPatchFindbugsWarningstez-dag.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/48//artifact/patchprocess/newPatchFindbugsWarningstez-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/48//artifact/patchprocess/newPatchFindbugsWarningstez-mapreduce.html
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/48//console
This message is automatically generated.
> Memory provided by *Context.getAvailableMemory needs to be setup explicitly
> ---------------------------------------------------------------------------
>
> Key: TEZ-1941
> URL: https://issues.apache.org/jira/browse/TEZ-1941
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: TEZ-1941.1.txt, TEZ-1941.2.txt
>
>
> *Contexts.getAvailableMemory rely on Runtime..getMaxMemory(). This doesn't
> work for memory scaling if multiple tasks are running within a JVM.
> Container sizes (sent over RPC) can be used for setting up this value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
