hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4883) TestCatalogTracker failing for me on ubuntu
Date Tue, 29 Nov 2011 07:11:41 GMT

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

Hudson commented on HBASE-4883:
-------------------------------

Integrated in HBase-TRUNK-security #13 (See [https://builds.apache.org/job/HBase-TRUNK-security/13/])
    HBASE-4883 TestCatalogTracker failing for me on ubuntu

stack : 
Files : 
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/catalog/TestCatalogTracker.java

                
> TestCatalogTracker failing for me on ubuntu
> -------------------------------------------
>
>                 Key: HBASE-4883
>                 URL: https://issues.apache.org/jira/browse/HBASE-4883
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>         Attachments: 4883.addendum, 4883.txt, tct.txt
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.apache.hadoop.hbase.catalog.TestCatalogTracker
> -------------------------------------------------------------------------------
> Tests run: 9, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.276 sec <<<
FAILURE!
> testNoTimeoutWaitForMeta(org.apache.hadoop.hbase.catalog.TestCatalogTracker)  Time elapsed:
1.051 sec  <<< ERROR!
> org.mockito.exceptions.misusing.WrongTypeOfReturnValue:
> Result cannot be returned by getConfiguration()
> getConfiguration() should return Configuration
>         at org.apache.hadoop.hbase.catalog.TestCatalogTracker.testNoTimeoutWaitForMeta(TestCatalogTracker.java:378)
>         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.runners.ParentRunner.runLeaf(ParentRunner.java:263)
>         at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
>         at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> {code}
> The above is strange since it seems to pass on jenkins and on macosx.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message