hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7343) Fix flaky condition for TestDrainingServer
Date Thu, 13 Dec 2012 01:39:21 GMT

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

Hadoop QA commented on HBASE-7343:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {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

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

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

This message is automatically generated.
> Fix flaky condition for TestDrainingServer
> ------------------------------------------
>                 Key: HBASE-7343
>                 URL: https://issues.apache.org/jira/browse/HBASE-7343
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.94.3
>            Reporter: Himanshu Vashishtha
>            Assignee: Himanshu Vashishtha
>            Priority: Minor
>         Attachments: HBASE-7343.patch
> The assert statement in setUpBeforeClass() may fail in case the region distribution is
not even (a particular rs has 0 regions).
> {code}
> junit.framework.AssertionFailedError
> 	at junit.framework.Assert.fail(Assert.java:48)
> 	at junit.framework.Assert.assertTrue(Assert.java:20)
> 	at junit.framework.Assert.assertFalse(Assert.java:34)
> 	at junit.framework.Assert.assertFalse(Assert.java:41)
> 	at org.apache.hadoop.hbase.TestDrainingServer.setUpBeforeClass(TestDrainingServer.java:83)
> {code}
> This is already fixed in trunk with HBASE-5992, but as that's a bigger change and uses
5877, this jira fixes that issue instead of backporting 5992.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message