hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7561) Make test-patch only run tests for changed modules
Date Wed, 24 Aug 2011 21:44:30 GMT

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

Hudson commented on HADOOP-7561:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #778 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/778/])
    HADOOP-7561. Make test-patch only run tests for changed modules.

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


> Make test-patch only run tests for changed modules
> --------------------------------------------------
>
>                 Key: HADOOP-7561
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7561
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Tom White
>            Assignee: Tom White
>             Fix For: 0.23.0
>
>         Attachments: HADOOP-7561.patch
>
>
> By running test-patch from trunk we can check that a change in one project (e.g. common)
doesn't cause compile errors in other projects (e.g. HDFS). To get this to work we only need
to run tests for the modules that are affected by the patch.

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

        

Mime
View raw message