hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11937) Guarantee a full build of all native code during pre-commit.
Date Sat, 09 May 2015 06:31:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-11937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536256#comment-14536256
] 

Haohui Mai commented on HADOOP-11937:
-------------------------------------

I think it's going to increase the jenkins running time to even longer -- it is not that common
to modify the the native code in most of the jiras.
Maybe we can consider take it off the critical path, by doing a full build if test-patch finds
out there are changes in the native code instead?

> Guarantee a full build of all native code during pre-commit.
> ------------------------------------------------------------
>
>                 Key: HADOOP-11937
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11937
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: scripts
>            Reporter: Chris Nauroth
>             Fix For: 2.8.0
>
>
> Some of the native components of the build are considered optional and either will not
build at all without passing special flags to Maven or will allow a build to proceed if dependencies
are missing from the build machine.  If these components do not get built, then pre-commit
isn't really providing full coverage of the build.  This issue proposes to update test-patch.sh
so that it does a full build of all native components.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message