[ https://issues.apache.org/jira/browse/TEZ-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532034#comment-14532034 ]
TezQA commented on TEZ-1961: ---------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12731077/TEZ-1961-2.patch against master revision 02870f0. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 3 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 2 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:red}-1 core tests{color}. The patch failed these unit tests in : org.apache.tez.dag.app.TestPreemption Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/647//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-TEZ-Build/647//artifact/patchprocess/newPatchFindbugsWarningstez-dag.html Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/647//console This message is automatically generated. > Remove misleading exception "No running dag" from AM logs > --------------------------------------------------------- > > Key: TEZ-1961 > URL: https://issues.apache.org/jira/browse/TEZ-1961 > Project: Apache Tez > Issue Type: Improvement > Reporter: Siddharth Seth > Assignee: Jeff Zhang > Priority: Critical > Attachments: TEZ-1961-1.patch, TEZ-1961-2.patch > > > {code} > 15/01/14 16:45:06 INFO ipc.Server: IPC Server handler 0 on 51000, call > org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolBlockingPB.getDAGStatus > from Call#0 Retry#0 > org.apache.tez.dag.api.TezException: No running dag at present > at > org.apache.tez.dag.api.client.DAGClientHandler.getDAG(DAGClientHandler.java:84) > at > org.apache.tez.dag.api.client.DAGClientHandler.getACLManager(DAGClientHandler.java:151) > at > org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolBlockingPBServerImpl.getDAGStatus(DAGClientAMProtocolBlockingPBServerImpl.java:94) > at > org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolRPC$DAGClientAMProtocol$2.callBlockingMethod(DAGClientAMProtocolRPC.java:7375) > at > org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:617) > at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:962) > at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2041) > at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2037) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657) > at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2035) > 15/01/14 16:45:06 INFO client.DAGClientImpl: DAG initialized: > CurrentState=Running > {code} > This exception shows up fairly often and isn't very relevant - queries before > a DAG is submitted to the AM. > This is very misleading, especially for folks new to Tez, and should be > removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)