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-7561) Make test-patch only run tests for changed modules
Date Fri, 19 Aug 2011 23:35:27 GMT

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

Tom White updated HADOOP-7561:
------------------------------

    Attachment: HADOOP-7561.patch

I tested this by running test-patch for

1. a patch containing changes to common, run from from trunk (with and without failing tests)
2. a patch containing changes to common and HDFS, run from trunk (with and without failing
tests)
3. a patch containing changes to common, run from common (with and without failing tests)

> 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