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

TezQA commented on TEZ-3433:
----------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12830096/TEZ-3433.patch
  against master revision 5c2f893.

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

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

This message is automatically generated.

> Tez UI: Searching using wrong ID causes error in all DAGs page
> --------------------------------------------------------------
>
>                 Key: TEZ-3433
>                 URL: https://issues.apache.org/jira/browse/TEZ-3433
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sushmitha Sreenivasan
>         Attachments: TEZ-3433.patch
>
>
> - In All DAGs page, DAG id uses an implementation separate from other search 
> parameters.
> - It throws error on trying to search with a wrong ID.
> - Fix the UI to display a "No records available!" message, similar to the one 
> we display on giving a wrong value in other fields.



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

Reply via email to