Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 23 Oct 2012 15:11:12 +0000 (UTC)
From: "Robert Joseph Evans (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <338975194.16210.1351005073041.JavaMail.jiratomcat@arcas>
In-Reply-To: <971198983.14322.1350959412057.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HADOOP-8964) test-patch.sh doesn't run all
 tests
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Joseph Evans commented on HADOOP-8964:
---------------------------------------------

We had a lot of speedup in the tests by doing this.  The problem is that running all tests takes hours.  This means that JIRAs start to back up and fill up the queues.  I am fine with changing it so it runs all of the tests for the top level project, like if it is in YARN it runs everything in YARN.  But if we want to enable all of the tests to run we first need to classify the tests between true unit tests that should be run as part of check-in/pre-commit and integration tests that take longer but should not be run as part of the pre-commit. i.e. anything that uses a minicluster. 
                
> 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