You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2014/11/14 15:22:34 UTC

[jira] [Commented] (HBASE-11698) TestFullLogReconstruction has duplicate config setting

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

Hadoop QA commented on HBASE-11698:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12681541/HBASE-11698.patch
  against trunk revision .
  ATTACHMENT ID: 12681541

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/11675//console

This message is automatically generated.

> TestFullLogReconstruction has duplicate config setting
> ------------------------------------------------------
>
>                 Key: HBASE-11698
>                 URL: https://issues.apache.org/jira/browse/HBASE-11698
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.98.5
>            Reporter: Sean Busbey
>            Priority: Trivial
>              Labels: beginner
>         Attachments: HBASE-11698.patch
>
>
> The 0.98 branch's version of TestFullLogReconstruction has a duplicate config setting during setupBeforeClass
> {code}
> 54    // faster failover with cluster.shutdown();fs.close() idiom
> 55    c.setInt("hbase.ipc.client.connect.max.retries", 1);
> 56    c.setInt("hbase.ipc.client.connect.max.retries", 1);
> {code}
> the 0.98.4 release has a line for setting this config and for the HDFS version. the branch-1 and master versions of this set of patches have only the setting of the hbase one, so I think that's the correct behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)