You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/03/12 00:33:39 UTC

[jira] [Resolved] (HADOOP-7650) Automated test for the tarballs

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

Allen Wittenauer resolved HADOOP-7650.
--------------------------------------
    Resolution: Later

Closing this as Later, but I suspect won't fix really, since that's what big top is supposed to be doing.

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)