[
https://issues.apache.org/jira/browse/HBASE-6824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547638#comment-13547638
]
Hadoop QA commented on HBASE-6824:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12563873/hbase-6824_v3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.TestLocalHBaseCluster
{color:red}-1 core zombie tests{color}. There are 8 zombie test(s):
at
org.apache.hadoop.hbase.master.TestMasterFailover.testMasterFailoverWithMockedRITOnDeadRS(TestMasterFailover.java:833)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/3943//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3943//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3943//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3943//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3943//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3943//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3943//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3943//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3943//console
This message is automatically generated.
> Introduce ${hbase.local.dir} and save coprocessor jars there
> ------------------------------------------------------------
>
> Key: HBASE-6824
> URL: https://issues.apache.org/jira/browse/HBASE-6824
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.3, 0.96.0
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Attachments: hbase-6824_v1-0.94.patch, hbase-6824_v1-trunk.patch,
> hbase-6824_v2-0.94.patch, hbase-6824_v2-trunk.patch, hbase-6824_v3.patch
>
>
> We need to make the temp directory where coprocessor jars are saved
> configurable. For this we will add hbase.local.dir configuration parameter.
> Windows tests are failing due to the pathing problems for coprocessor jars:
> Two HBase TestClassLoading unit tests failed due to a failiure in loading the
> test file from HDFS:
> {code}
> testClassLoadingFromHDFS(org.apache.hadoop.hbase.coprocessor.TestClassLoading):
> Class TestCP1 was missing on a region
> testClassLoadingFromLibDirInJar(org.apache.hadoop.hbase.coprocessor.TestClassLoading):
> Class TestCP1 was missing on a region
> {code}
> The problem is that CoprocessorHost.load() copies the jar file locally, and
> schedules the local file to be deleted on exit, but calling
> FileSystem.deleteOnExit(). However, the filesystem is not the file system of
> the local file, it is the distributed file system, so on windows, the Path
> fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
