Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 1 Jun 2012 00:11:23 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <1216407264.24571.1338509483302.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <670992729.18038.1338408863096.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HDFS-3479) backport HDFS-3335 (check for edit
 log corruption at the end of the log) to branch-1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287054#comment-13287054 ] 

Hadoop QA commented on HDFS-3479:
---------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12530479/HDFS-3479-b1.002.patch
  against trunk revision .

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

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

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

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2561//console

This message is automatically generated.
                
> backport HDFS-3335 (check for edit log corruption at the end of the log) to branch-1
> ------------------------------------------------------------------------------------
>
>                 Key: HDFS-3479
>                 URL: https://issues.apache.org/jira/browse/HDFS-3479
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>         Attachments: HDFS-3335-b1.005.patch, HDFS-3479-b1.002.patch
>
>
> backport HDFS-3335 (check for edit log corruption at the end of the log) to branch-1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira