hadoop-common-issues mailing list archives

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

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

Allen Wittenauer commented on HADOOP-11937:
-------------------------------------------

Playing around with a new build of HADOOP-11929 has seemed to indicate the key problem we've
got is that cmake progress reports are non-deterministic.  If a patch changes how long something
takes, it throws the whole works off because the injected % indicators change.  So the first
thing we need to do is have a way for test-patch to disable that.  Otherwise we're going to
continually have false positives.

> 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
>
> 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