[
https://issues.apache.org/jira/browse/TEZ-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098706#comment-15098706
]
TezQA commented on TEZ-3037:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12782330/TEZ-3037.1.patch
against master revision b656157.
{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:red}-1 findbugs{color}. The patch appears to introduce 1 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.test.TestFaultTolerance
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1422//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/1422//artifact/patchprocess/newPatchFindbugsWarningstez-dag.html
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1422//console
This message is automatically generated.
> History URL should be set regardless of which history logging service is
> enabled
> --------------------------------------------------------------------------------
>
> Key: TEZ-3037
> URL: https://issues.apache.org/jira/browse/TEZ-3037
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Hitesh Shah
> Assignee: Hitesh Shah
> Attachments: TEZ-3037.1.patch, TEZ-3037.2.patch
>
>
> It would be simpler and safer to always set the history url regardless of
> whether the history logger supports a UI or not. The more common instance of
> deployment will be that the history logger will be ATS based.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
