[ https://issues.apache.org/jira/browse/TEZ-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974335#comment-15974335 ]
TezQA commented on TEZ-3688: ---------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12863969/TEZ-3688.1.patch against master revision f355a05. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {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 1 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/2375//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-TEZ-Build/2375//artifact/patchprocess/newPatchFindbugsWarningsjob-analyzer.html Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2375//console This message is automatically generated. > Add analyzer to provide the set of machines that participated in the vertex > and the number of tasks that ran on that node > ------------------------------------------------------------------------------------------------------------------------- > > Key: TEZ-3688 > URL: https://issues.apache.org/jira/browse/TEZ-3688 > Project: Apache Tez > Issue Type: Bug > Reporter: Nita Dembla > Assignee: Rajesh Balamohan > Attachments: TEZ-3688.1.patch > > > Need an analyzer to parse DAG info and outputs the how many tasks of a vertex > ran on a node. This would help in isolating task scheduling issues. -- This message was sent by Atlassian JIRA (v6.3.15#6346)