hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-7612) Change test-patch to run tests for all nested modules
Date Mon, 05 Sep 2011 23:06:09 GMT

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

Tom White updated HADOOP-7612:

    Attachment: HADOOP-7612.patch

This patch makes a change to test top-level compilation, and run all tests under the base
directory it is run from (or specified in --basedir). It also add a --run-tests option so
developers can run tests using test-patch. 

> Change test-patch to run tests for all nested modules
> -----------------------------------------------------
>                 Key: HADOOP-7612
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7612
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>            Reporter: Tom White
>            Assignee: Tom White
>         Attachments: HADOOP-7612.patch
> HADOOP-7561 changed the behaviour of test-patch to run tests for changed modules, however
this was assuming a flat structure. Given the nested maven hierarchy we should always run
all the common tests for any common change, all the HDFS tests for any HDFS change, and all
the MapReduce tests for any MapReduce change.
> In addition, we should do a top-level build to test compilation after any change.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message