[ 
https://issues.apache.org/jira/browse/TEZ-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519598#comment-14519598
 ] 

TezQA commented on TEZ-2386:
----------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12729184/TEZ-2386.2.patch
  against master revision 9ba4b1b.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 4 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 2.0.3) 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/578//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/578//console

This message is automatically generated.

> Tez UI: Inconsistent usage of icon colors
> -----------------------------------------
>
>                 Key: TEZ-2386
>                 URL: https://issues.apache.org/jira/browse/TEZ-2386
>             Project: Apache Tez
>          Issue Type: Bug
>          Components: UI
>            Reporter: Prakash Ramachandran
>            Assignee: Prakash Ramachandran
>         Attachments: TEZ-2386.1.patch, TEZ-2386.2.patch, TEZ-2386.wip.1.patch
>
>
> if there's failed attempts in a DAG, and it succeeds - an orange icon shows 
> up on the DAG page. This is very useful to identify DAGs which may need some 
> debugging.
> However, the color is Green for Vertex / Task views after this - so it's 
> difficult to know which one actually had problems.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to