[
https://issues.apache.org/jira/browse/TEZ-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15979290#comment-15979290
]
TezQA commented on TEZ-3690:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12864545/TEZ-3690.2.patch
against master revision ca607d6.
{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: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 :
org.apache.tez.test.TestRecovery
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2387//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2387//console
This message is automatically generated.
> Tez on hadoop 3 build failed due to hdfs client/server jar separation
> ---------------------------------------------------------------------
>
> Key: TEZ-3690
> URL: https://issues.apache.org/jira/browse/TEZ-3690
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Junping Du
> Assignee: Junping Du
> Priority: Blocker
> Fix For: 0.9.0
>
> Attachments: TEZ-3690.2.patch, TEZ-3690.patch
>
>
> Build TEZ master branch against hadoop 3 alpha 3 (trunk branch), and found
> issues:
> {noformat}
> ...
> api/src/test/java/org/apache/tez/common/TestTezCommonUtils.java:[62,42]
> cannot access org.apache.hadoop.hdfs.DistributedFileSystem
> {noformat}
> This is due to HDFS-6200 that we are separating client and server jars. We
> should fix downstream projects for this change.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
