Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Sat, 17 Sep 2011 00:25:08 +0000 (UTC)
From: "Eli Collins (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <136389392.37402.1316219108912.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HADOOP-7650) Automated test for the tarballs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Automated test for the tarballs
-------------------------------

                 Key: HADOOP-7650
                 URL: https://issues.apache.org/jira/browse/HADOOP-7650
             Project: Hadoop Common
          Issue Type: Bug
          Components: test
            Reporter: Eli Collins


Currently we don't test the generated tarball so we don't automatically detect changes that break the artifact generation or bin scripts (eg HADOOP-7356). We should have a simple functional test run from Jenkins that covers this stuff.

I wrote some simple automation for 20x tarballs that starts a pseudo cluster with multiple DNs and TTs and runs basic HDFS commands and MR jobs (with and w/o the LinuxTaskController) that could be used as a starting point. Code lives here: https://github.com/elicollins/hadoop-dev/tree/pseudo

Eric also added a lot of cluster config generation in HADOOP-7599 that could be used as a starting point as well.

This should also support trunk (Yarn) of course.

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