Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <3994386.220731284616293068.JavaMail.jira@thor>
Date: Thu, 16 Sep 2010 01:51:33 -0400 (EDT)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Updated: (MAPREDUCE-2073) TestTrackerDistributedCacheManager
 should be up-front about requirements on build environment
In-Reply-To: <2632903.220661284615640077.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon updated MAPREDUCE-2073:
-----------------------------------

    Attachment: mapreduce-2073.txt

Patch for trunk.

Tested by chmod 700 $HOME, then running tests. It used to be that it would fail in a non-obvious manner, now I get a nice message telling me my permissions are wrong. Then I did chmod a+x $HOME and the tests pass.

> TestTrackerDistributedCacheManager should be up-front about requirements on build environment
> ---------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2073
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2073
>             Project: Hadoop Map/Reduce
>          Issue Type: Test
>          Components: distributed-cache, test
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Trivial
>         Attachments: mapreduce-2073-0.20.txt, mapreduce-2073.txt
>
>
> TestTrackerDistributedCacheManager will fail on a system where the build directory is in any path where an ancestor doesn't have a+x permissions. On one of our hudson boxes, for example, hudson's workspace had 700 permissions and caused this test to fail reliably, but not in an obvious manner. It would be helpful if the test failed with a more obvious error message during setUp() when the build environment is misconfigured.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.