[
https://issues.apache.org/jira/browse/TEZ-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533771#comment-14533771
]
TezQA commented on TEZ-2421:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12731341/TEZ-2421.2.patch
against master revision 05f77fe.
{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 2.0.3) 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.dag.impl.TestDAGImpl
Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/653//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/653//console
This message is automatically generated.
> Deadlock in AM because attempt and vertex locking each other out
> ----------------------------------------------------------------
>
> Key: TEZ-2421
> URL: https://issues.apache.org/jira/browse/TEZ-2421
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Priority: Blocker
> Attachments: TEZ-2421.1.patch, TEZ-2421.2.patch
>
>
> Ideally locks should be taken one way - either going down or up. Preferably
> not going up because most such data can be passed in during object
> construction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
