hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Boudnik (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6374) JUnit tests should never depend on anything in conf
Date Thu, 21 Jan 2010 05:58:56 GMT

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

Konstantin Boudnik updated HADOOP-6374:
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.22.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

I've just committed this to the trunk. Thanks Anatoli!

> JUnit tests should never depend on anything in conf
> ---------------------------------------------------
>
>                 Key: HADOOP-6374
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6374
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: test
>            Reporter: Owen O'Malley
>            Assignee: Anatoli Fomenko
>            Priority: Blocker
>             Fix For: 0.22.0
>
>         Attachments: HADOOP-6374.patch
>
>
> The recent change to mapred-queues.xml that causes many mapreduce tests to break unless
you delete conf/mapred-queues.xml out of your build tree is bad. We need to make sure that
nothing in conf is used in the unit tests. One potential solution is to copy the templates
into build/test/conf and use that instead.

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


Mime
View raw message