[
https://issues.apache.org/jira/browse/TEZ-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255012#comment-15255012
]
TezQA commented on TEZ-3219:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12800324/TEZ-3219.4.patch
against master revision a425f5d.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified test files.
{color:red}-1 javac{color}. The applied patch generated 45 javac
compiler warnings (more than the master's current 33 warnings).
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:red}-1 findbugs{color}. The patch appears to introduce 2 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.TestContainerReuse
org.apache.tez.test.TestFaultTolerance
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1674//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/1674//artifact/patchprocess/newPatchFindbugsWarningstez-dag.html
Javac warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/1674//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1674//console
This message is automatically generated.
> Allow service plugins to define log locations link for remotely run task
> attempts
> ----------------------------------------------------------------------------------
>
> Key: TEZ-3219
> URL: https://issues.apache.org/jira/browse/TEZ-3219
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Hitesh Shah
> Assignee: Hitesh Shah
> Attachments: TEZ-3219.1.patch, TEZ-3219.2.patch, TEZ-3219.3.patch,
> TEZ-3219.4.patch
>
>
> Today log links are generated based on the assumption that they are running
> in yarn containers. For LLAP-like service plugin runs, the log links are
> incorrect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
