hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7597) TestHBaseFsck#testRegionShouldNotBeDeployed seems to be flaky
Date Tue, 19 Mar 2013 02:33:17 GMT

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

Hudson commented on HBASE-7597:
-------------------------------

Integrated in HBase-TRUNK #3970 (See [https://builds.apache.org/job/HBase-TRUNK/3970/])
    HBASE-7597 TestHBaseFsck#testRegionShouldNotBeDeployed seems to be flaky (Revision 1458059)

     Result = SUCCESS
jxiang : 
Files : 
* /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java

                
> TestHBaseFsck#testRegionShouldNotBeDeployed seems to be flaky
> -------------------------------------------------------------
>
>                 Key: HBASE-7597
>                 URL: https://issues.apache.org/jira/browse/HBASE-7597
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jean-Marc Spaggiari
>            Assignee: Jimmy Xiang
>             Fix For: 0.95.0, 0.98.0
>
>         Attachments: trunk-7597.patch
>
>
> I ran the entire test suite many times and always failed on, at least, testRegionShouldNotBeDeployed.
> Results below. I will attached more result when current tests are done.
> Failed tests:
> testDeleteExpiredStoreFiles(org.apache.hadoop.hbase.regionserver.TestStore):
> expected:<2> but was:<4>
>   testAcquireTaskAtStartup(org.apache.hadoop.hbase.regionserver.TestSplitLogWorker):
> Waiting timed out after [1 000] msec
>   testRegionShouldNotBeDeployed(org.apache.hadoop.hbase.util.TestHBaseFsck):
> expected:<[SHOULD_NOT_BE_DEPLOYED]> but was:<[]>
>   testPermissionsWatcher(org.apache.hadoop.hbase.security.access.TestZKPermissionsWatcher)

--
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

Mime
View raw message