[
https://issues.apache.org/jira/browse/TEZ-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15652435#comment-15652435
]
TezQA commented on TEZ-3534:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12838256/TEZ-3534.01.patch
against master revision 4b62875.
{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:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2099//console
This message is automatically generated.
> Differentiate thread names on Fetchers, minor changes to shuffle shutdown code
> ------------------------------------------------------------------------------
>
> Key: TEZ-3534
> URL: https://issues.apache.org/jira/browse/TEZ-3534
> Project: Apache Tez
> Issue Type: Task
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: TEZ-3534.01.patch
>
>
> Follow up to https://issues.apache.org/jira/browse/TEZ-3533.
> Adding some exception checks during shutdown could help with ensuring all
> components shutdown, in case there is a failure from a previous one.
> Rename threads is to make it easier to debug from stacktraces.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
