[ https://issues.apache.org/jira/browse/TEZ-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741206#comment-14741206 ]
TezQA commented on TEZ-2787: ---------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12755426/TEZ-2787.3.patch against master revision b288be7. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 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:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 3.0.1) 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/1116//testReport/ Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1116//console This message is automatically generated. > Tez AM should have java.io.tmpdir=./tmp to be consistent with tasks > ------------------------------------------------------------------- > > Key: TEZ-2787 > URL: https://issues.apache.org/jira/browse/TEZ-2787 > Project: Apache Tez > Issue Type: Bug > Affects Versions: 0.7.0 > Reporter: Jason Lowe > Assignee: Jonathan Eagles > Attachments: TEZ-2787.1.patch, TEZ-2787.2.patch, TEZ-2787.3.patch > > > TezRuntimeChildJVM ensures that tasks are launched with > -Djava.io.tmpdir=./tmp, but there's no corresponding code to ensure the Tez > AM also has a similar tmpdir setting. The client should setup the AM launch > context to have -Djava.io.tmpdir=./tmp to be consistent with the tasks and to > prevent accidental leaking of files in /tmp by the Tez AM if it crashes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)