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

Ted Yu commented on HBASE-7299:
-------------------------------

hadoop4 environment has problem: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3751/consoleFull

The patch only touches TestMultiParallel which wouldn't have effect on other 
tests.
{code}
Running org.apache.hadoop.hbase.client.TestHCM
2012-12-30 09:01:55.167 java[734:1203] Unable to load realm info from 
SCDynamicStore
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.993 sec
{code}
Integrated to trunk.

Thanks for the patch, Chunhui.

Thanks for the review, Stack.
                
> TestMultiParallel fails intermittently in trunk builds
> ------------------------------------------------------
>
>                 Key: HBASE-7299
>                 URL: https://issues.apache.org/jira/browse/HBASE-7299
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: chunhui shen
>            Priority: Critical
>             Fix For: 0.96.0
>
>         Attachments: 7299-v4.txt, HBASE-7299.patch, HBASE-7299v2.patch, 
> HBASE-7299v3.patch
>
>
> From trunk build #3598:
> {code}
>  testFlushCommitsNoAbort(org.apache.hadoop.hbase.client.TestMultiParallel): 
> Count of regions=8
> {code}
> It failed in 3595 as well:
> {code}
> java.lang.AssertionError: Server count=2, abort=true expected:<1> but was:<2>
>       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.apache.hadoop.hbase.client.TestMultiParallel.doTestFlushCommits(TestMultiParallel.java:267)
>       at 
> org.apache.hadoop.hbase.client.TestMultiParallel.testFlushCommitsWithAbort(TestMultiParallel.java:226)
> {code}

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

Reply via email to