[
https://issues.apache.org/jira/browse/TEZ-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364914#comment-15364914
]
TezQA commented on TEZ-3325:
----------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816464/TEZ-3325.1.patch
against master revision befc426.
{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/1830//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1830//console
This message is automatically generated.
> Flaky test in TestDAGImpl.testCounterLimits
> -------------------------------------------
>
> Key: TEZ-3325
> URL: https://issues.apache.org/jira/browse/TEZ-3325
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Zhiyuan Yang
> Assignee: Zhiyuan Yang
> Attachments: TEZ-3325.1.patch
>
>
> This test manually set more than TEZ_COUNTERS_MAX counters across three
> vertices to trigger dag failure, but sometimes dag still succeeds. The reason
> is dag may already finish before we set last vertice counters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
