[
https://issues.apache.org/jira/browse/TEZ-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645647#comment-14645647
]
TezQA commented on TEZ-2645:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12747729/TEZ-2645.3.patch
against master revision cf40088.
{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/937//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/937//console
This message is automatically generated.
> Provide standard analyzers for job analysis
> -------------------------------------------
>
> Key: TEZ-2645
> URL: https://issues.apache.org/jira/browse/TEZ-2645
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Rajesh Balamohan
> Assignee: Rajesh Balamohan
> Attachments: TEZ-2645.1.patch, TEZ-2645.2.patch, TEZ-2645.3.patch
>
>
> TEZ-2076 provided a way in which job history data can be parsed/normalized
> and represented in-memory. Based on this, standard set of analyzers (e.g
> ContainerReuseAnalyzer, LocalityAnalyzer, SlowNodeAnalyzer etc) can provided
> in tez-tools for job analysis. Results can be stored in CSVResult which could
> be rendered differently based on UI requirements.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)