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-8920) TestZKBasedOpenCloseRegion.testReOpenRegion fails occasionally
Date Wed, 10 Jul 2013 20:23:48 GMT

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

Hadoop QA commented on HBASE-8920:

{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 6 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/6299//console

This message is automatically generated.
> TestZKBasedOpenCloseRegion.testReOpenRegion fails occasionally
> --------------------------------------------------------------
>                 Key: HBASE-8920
>                 URL: https://issues.apache.org/jira/browse/HBASE-8920
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>         Attachments: 8920.txt, 8920v2.txt
> Failed here:
> https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/607/testReport/org.apache.hadoop.hbase.master/TestZKBasedOpenCloseRegion/testReOpenRegion/
> and
> https://builds.apache.org/job/HBase-TRUNK/4232/testReport/org.apache.hadoop.hbase.master/TestZKBasedOpenCloseRegion/testReOpenRegion/
> In both cases, we fail for the same reason.  The previous test closes a region.  The
failing test starts but we are reopening the region we'd just closed as we are wont to do.
 This is the region that gets chosen by the failing test to practise reopen on only  it is
not yet fully open so in comes the close and it gets stomped on by the ongoing open.
> Let me post some log.

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