hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhou wenjian (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7079) testCloseRegionWhenEncodedRegionNameIsNotGiven occainlly fails
Date Wed, 31 Oct 2012 05:55:12 GMT

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

Zhou wenjian commented on HBASE-7079:
-------------------------------------

patch for trunk
                
> testCloseRegionWhenEncodedRegionNameIsNotGiven occainlly fails
> --------------------------------------------------------------
>
>                 Key: HBASE-7079
>                 URL: https://issues.apache.org/jira/browse/HBASE-7079
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.94.2
>            Reporter: Zhou wenjian
>            Assignee: Zhou wenjian
>         Attachments: HBASE-7079-trunk.patch, HBASE-7079-trunk-v2.patch
>
>
> Regression
> org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven
> Failing for the past 1 build (Since #147 )
> Took 2 ms.
> Error Message
> -1
> Stacktrace
> java.lang.ArrayIndexOutOfBoundsException: -1
> 	at java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:343)
> 	at java.util.Collections$UnmodifiableList.get(Collections.java:1154)
> 	at org.apache.hadoop.hbase.HBaseTestingUtility.getRSForFirstRegionInTable(HBaseTestingUtility.java:1300)
> 	at org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven(TestAdmin.java:1454)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> 	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> 	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
> 	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:47)
> 	at org.junit.rules.RunRules.evaluate(RunRules.java:18)
> 	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> 	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> 	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> 	at org.junit.runners.Suite.runChild(Suite.java:128)
> 	at org.junit.runners.Suite.runChild(Suite.java:24)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:662)

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