hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jimmy Xiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6715) TestFromClientSide.testCacheOnWriteEvictOnClose is flaky
Date Thu, 06 Sep 2012 16:47:08 GMT

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

Jimmy Xiang commented on HBASE-6715:
------------------------------------

Sure, committed it to trunk and 0.94. We will see if the issue is gone.
                
> TestFromClientSide.testCacheOnWriteEvictOnClose is flaky
> --------------------------------------------------------
>
>                 Key: HBASE-6715
>                 URL: https://issues.apache.org/jira/browse/HBASE-6715
>             Project: HBase
>          Issue Type: Test
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>         Attachments: trunk-6715.patch
>
>
> Occasionally, this test fails:
> {noformat}
> expected:<2049> but was:<2069>
> Stacktrace
> java.lang.AssertionError: expected:<2049> but was:<2069>
> at org.junit.Assert.fail(Assert.java:93)
> at org.junit.Assert.failNotEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:128)
> at org.junit.Assert.assertEquals(Assert.java:472)
> at org.junit.Assert.assertEquals(Assert.java:456)
> at org.apache.hadoop.hbase.client.TestFromClientSide.testCacheOnWriteEvictOnClose(TestFromClientSide.java:4248)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {noformat}
> It could be because there is other thread still accessing the cache.

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