[
https://issues.apache.org/jira/browse/TEZ-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15655146#comment-15655146
]
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/12838419/TEZ-3534.03.patch
against master revision a93dbf0.
{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:red}-1 core tests{color}. The following test timeouts occurred in :
Tests
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2102//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2102//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, TEZ-3534.02.patch, TEZ-3534.03.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)
