You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "TezQA (JIRA)" <ji...@apache.org> on 2016/09/12 11:38:20 UTC

[jira] [Commented] (TEZ-3434) Add unit tests for flush events and interval with recovery

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

TezQA commented on TEZ-3434:
----------------------------

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

    {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/1964//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1964//console

This message is automatically generated.

> Add unit tests for flush events and interval with recovery
> ----------------------------------------------------------
>
>                 Key: TEZ-3434
>                 URL: https://issues.apache.org/jira/browse/TEZ-3434
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Harish Jaiprakash
>            Assignee: Harish Jaiprakash
>         Attachments: TEZ-3434.01.patch
>
>
> Test tez.dag.recovery.max.unflushed.events and tez.dag.recovery.flush.interval.secs properties and verify that:
> * Events gets flushed when either of the properties gets satisfied.
> * When one of the property is set to invalid value (-1) , It should respect other property and flush the content
> * Apart from these two properties, the events get flushed when certain specific event occurs like DAG start/stop, commit



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