[
https://issues.apache.org/jira/browse/TEZ-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975897#comment-15975897
]
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/12864175/TEZ-3690.patch
against master revision fb0e45b.
{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/2382//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.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)
