Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <4161083.203041295996625806.JavaMail.jira@thor>
Date: Tue, 25 Jan 2011 18:03:45 -0500 (EST)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-7118) NPE in Configuration.writeXml
In-Reply-To: <25553485.202661295995906384.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hadoop QA commented on HADOOP-7118:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12469351/hadoop-7118.txt
  against trunk revision 1063090.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/198//console

This message is automatically generated.

> NPE in Configuration.writeXml
> -----------------------------
>
>                 Key: HADOOP-7118
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7118
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Blocker
>             Fix For: 0.22.0
>
>         Attachments: hadoop-7118.txt
>
>
> In HADOOP-7082 I stupidly introduced a regression whereby Configuration.writeXml will throw an NPE if it is called before any .get() call is made, since the properties member is not initialized. This is causing a failure in TestCapacitySchedulerWithJobTracker on my box, but doesn't appear to trigger any failures in the non-contrib tests since .get() is usually called first.
> This JIRA is to fix the bug and add a unit test for writeXml in common (apparently it never had a unit test)

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