[
https://issues.apache.org/jira/browse/HADOOP-8964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482412#comment-13482412
]
Tom White commented on HADOOP-8964:
-----------------------------------
There was some discussion on this on
http://mail-archives.aurora.apache.org/mod_mbox/hadoop-common-dev/201204.mbox/%3ccaf-wd4tvkwypuuq9ibxv4uz8b2behxnpfkb5mq3d-pwvksh...@mail.gmail.com%3E
and HADOOP-8308.
I like the direction that Bobby is suggesting. We could use Maven's distinction
between unit and integration tests ({{mvn test}} vs {{mvn integration-test}}).
> test-patch.sh doesn't run all tests
> -----------------------------------
>
> Key: HADOOP-8964
> URL: https://issues.apache.org/jira/browse/HADOOP-8964
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
>
> test-patch.sh tries to be smart but with bad results. When it runs tests, say
> on each commit, it only runs tests only from modules which have corresponding
> changes. This is a cause of concern for downstream modules. We ran into
> multiple issues in the past because of this, the most recent of it being
> YARN-179.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
