[
https://issues.apache.org/jira/browse/TEZ-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517464#comment-16517464
]
TezQA commented on TEZ-3934:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12928389/TEZ-3934.003.patch
against master revision 3f2373e.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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.dag.app.rm.TestTaskScheduler
The following test timeouts occurred in :
org.apache.tez.test.TestRecovery
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2842//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2842//console
This message is automatically generated.
> LegacySpeculator sometime issues wrong number of speculative attempts
> ---------------------------------------------------------------------
>
> Key: TEZ-3934
> URL: https://issues.apache.org/jira/browse/TEZ-3934
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Jonathan Eagles
> Assignee: Nishant Dash
> Priority: Major
> Attachments: TEZ-3934.001.patch, TEZ-3934.002.patch,
> TEZ-3934.003.patch, TestSpeculation-output.txt
>
>
> Attaching a log from TestSpeculation that shows two speculative events
> launched instead of just a single one. I have seen this in practice and not
> just in tests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
