[jira] [Updated] (HADOOP-10114) jenkins tried to test hadoop-hdfs without building the native code in hadoop-common

["Colin Patrick McCabe (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-10114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colin Patrick McCabe updated HADOOP-10114:
------------------------------------------

    Summary: jenkins tried to test hadoop-hdfs without building the native code in hadoop-common  (was: TestHdfsNativeCodeLoader should reside in hadoop-common instead of hadoop-hdfs)

> jenkins tried to test hadoop-hdfs without building the native code in hadoop-common
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-10114
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10114
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>         Attachments: HADOOP-10114.000.patch
>
>
> TestHdfsNativeCodeLoader tests whether Java is able to load the native library libhadoop.so.
> However, it is the hadoop-common project, rather than the hadoop-hdfs project that creates this library during the build. Therefore this unit test will complain that it cannot find the library if Jenkins does not rebuild hadoop-common.
> HDFS-3987 is an example that hits this bug.The patch touches hadoop-auth and hadoop-hdfs. Jenkins decides it won't built hadoop-common, thus the unit test fails simply complaining about it cannot find libhadoop.so.
> The log of the build can be found at https://builds.apache.org/job/PreCommit-HDFS-Build/5470/consoleFull
> We can avoid this problem by moving the unit test to hadoop-common, or we can remove this unit test since TestNativeCodeLoader in hadoop-common has already covered the same case.



--
This message was sent by Atlassian JIRA
(v6.1#6144)