[
https://issues.apache.org/jira/browse/HADOOP-8964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482757#comment-13482757
]
Vinod Kumar Vavilapalli commented on HADOOP-8964:
-------------------------------------------------
I am definitely for not running mapreduce tests when a common patch gets
checked in. But if YARN common lib changes, I definitely want to run RM and NM
tests. I understand that not running everything speeds things up, but we have
correctness issues when we don't run downstream tests.
Is it okay to just run all tests in case of YARN for the shorter term, they
don't take more than 10 mins for now? Separating integration tests into their
own suite is a bigger effort.
> 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
