hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17495) TestHRegionWithInMemoryFlush#testFlushCacheWhileScanning intermittently fails due to assertion error
Date Thu, 02 Mar 2017 06:16:45 GMT

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

ramkrishna.s.vasudevan commented on HBASE-17495:
------------------------------------------------

Not able to generate failure even after running the script for 20 times. Also in the trunk
build this test is not in the flaky tests list which means it has been consistent there? 

> TestHRegionWithInMemoryFlush#testFlushCacheWhileScanning intermittently fails due to
assertion error
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-17495
>                 URL: https://issues.apache.org/jira/browse/HBASE-17495
>             Project: HBase
>          Issue Type: Test
>            Reporter: Ted Yu
>            Priority: Critical
>         Attachments: 17495-dbg.txt, 17495-testHRegionWithInMemoryFlush-output-2.0123,
testHRegionWithInMemoryFlush-flush-output.0123, TestHRegionWithInMemoryFlush-out.0222.tar.gz,
TestHRegionWithInMemoryFlush-out.0301, testHRegionWithInMemoryFlush-output.0119
>
>
> Looping through the test (based on commit 76dc957f64fa38ce88694054db7dbf590f368ae7),
I saw the following test failure:
> {code}
> testFlushCacheWhileScanning(org.apache.hadoop.hbase.regionserver.TestHRegionWithInMemoryFlush)
 Time elapsed: 0.53 sec  <<< FAILURE!
> java.lang.AssertionError: toggle=false i=940 ts=1484852861597 expected:<94> but
was:<92>
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotEquals(Assert.java:834)
>   at org.junit.Assert.assertEquals(Assert.java:645)
>   at org.apache.hadoop.hbase.regionserver.TestHRegion.testFlushCacheWhileScanning(TestHRegion.java:3533)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> {code}
> See test output for details.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message