[
https://issues.apache.org/jira/browse/TEZ-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101627#comment-16101627
]
TezQA commented on TEZ-3805:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12878979/TEZ-3805.1.patch
against master revision 5d78833.
{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: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/2588//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2588//console
This message is automatically generated.
> Analyzer: Add an analyzer to find out scheduling misses in 1:1 edges
> --------------------------------------------------------------------
>
> Key: TEZ-3805
> URL: https://issues.apache.org/jira/browse/TEZ-3805
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Rajesh Balamohan
> Assignee: Rajesh Balamohan
> Attachments: TEZ-3805.1.patch
>
>
> When 1:1 edge is used, it would be helpful to find out whether downstream
> tasks ran on the same location provided in the hints by the runtime.
> One of the recent feature in upstream project (hive) used 1:1 edge. Instead
> of checking the logs, it would be useful to have an analyzer to churn out the
> details.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)