[
https://issues.apache.org/jira/browse/HBASE-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang updated HBASE-6715:
-------------------------------
Attachment: trunk-6715.patch
> 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
