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

TezQA commented on TEZ-3007:
----------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12868247/TEZ-3007.03.patch
  against master revision 6317725.

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

    {color:green}+1 tests included{color}.  The patch appears to include 3 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:red}-1 core tests{color}.  The patch failed these unit tests in :
                   
org.apache.tez.runtime.library.common.writers.TestUnorderedPartitionedKVWriter

Test results: 
https://builds.apache.org/job/PreCommit-TEZ-Build/2456//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2456//console

This message is automatically generated.

> Use AppFinalState.ENDED when unregistering with the RM in session mode
> ----------------------------------------------------------------------
>
>                 Key: TEZ-3007
>                 URL: https://issues.apache.org/jira/browse/TEZ-3007
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>            Assignee: Harish Jaiprakash
>         Attachments: TEZ-3007.01.patch, TEZ-3007.02.patch, TEZ-3007.03.patch
>
>
> YARN-4207 adds appFinalState.ENDED. When running in session mode - Tez should 
> make use of this state instead of setting success or failure - since the app 
> final state does not indicate anything about the potentially multiple queries 
> which executed in the app.
> ShimSupport added earlier should facilitate this.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to