You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2011/09/05 21:58:12 UTC

[jira] [Created] (HADOOP-7612) Change test-patch to run tests for all nested modules

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


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

        

[jira] [Commented] (HADOOP-7612) Change test-patch to run tests for all nested modules

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100560#comment-13100560 ] 

Hudson commented on HADOOP-7612:
--------------------------------

Integrated in Hadoop-Common-trunk-Commit #850 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/850/])
    HADOOP-7612. Change test-patch to run tests for all nested modules.

tomwhite : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1166848
Files : 
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> 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

        

[jira] [Commented] (HADOOP-7612) Change test-patch to run tests for all nested modules

Posted by "Aaron T. Myers (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097669#comment-13097669 ] 

Aaron T. Myers commented on HADOOP-7612:
----------------------------------------

+1, the patch looks good to me. Thanks a lot for doing this, Tom.

> 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

        

[jira] [Commented] (HADOOP-7612) Change test-patch to run tests for all nested modules

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100566#comment-13100566 ] 

Hudson commented on HADOOP-7612:
--------------------------------

Integrated in Hadoop-Hdfs-trunk-Commit #927 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/927/])
    HADOOP-7612. Change test-patch to run tests for all nested modules.

tomwhite : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1166848
Files : 
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> 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

        

[jira] [Commented] (HADOOP-7612) Change test-patch to run tests for all nested modules

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100562#comment-13100562 ] 

Hudson commented on HADOOP-7612:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #861 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/861/])
    HADOOP-7612. Change test-patch to run tests for all nested modules.

tomwhite : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1166848
Files : 
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> 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

        

[jira] [Resolved] (HADOOP-7612) Change test-patch to run tests for all nested modules

Posted by "Tom White (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White resolved HADOOP-7612.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.23.0
     Hadoop Flags: [Reviewed]

I've just committed this.

> 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
>             Fix For: 0.23.0
>
>         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

        

[jira] [Commented] (HADOOP-7612) Change test-patch to run tests for all nested modules

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100650#comment-13100650 ] 

Hudson commented on HADOOP-7612:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk #811 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/811/])
    HADOOP-7612. Change test-patch to run tests for all nested modules.

tomwhite : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1166848
Files : 
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> 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
>             Fix For: 0.23.0
>
>         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

        

[jira] [Updated] (HADOOP-7612) Change test-patch to run tests for all nested modules

Posted by "Tom White (JIRA)" <ji...@apache.org>.
     [ 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

        

[jira] [Commented] (HADOOP-7612) Change test-patch to run tests for all nested modules

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101160#comment-13101160 ] 

Hudson commented on HADOOP-7612:
--------------------------------

Integrated in Hadoop-Hdfs-trunk #788 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/788/])
    HADOOP-7612. Change test-patch to run tests for all nested modules.

tomwhite : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1166848
Files : 
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> 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
>             Fix For: 0.23.0
>
>         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