You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Himanshu Vashishtha (JIRA)" <ji...@apache.org> on 2012/12/28 07:04:13 UTC

[jira] [Commented] (HBASE-7447) Occasional failures of TestSplitLogWorker#testAcquireTaskAtStartup

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

Himanshu Vashishtha commented on HBASE-7447:
--------------------------------------------

What's the stack trace? HBASE-6528 might be related.
                
> Occasional failures of TestSplitLogWorker#testAcquireTaskAtStartup
> ------------------------------------------------------------------
>
>                 Key: HBASE-7447
>                 URL: https://issues.apache.org/jira/browse/HBASE-7447
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.94.4
>            Reporter: Andrew Purtell
>
> I see occasional failures (1 out of ~20) on branch 0.94 of TestSplitLogWorker#testAcquireTaskAtStartup
> {noformat}
> Running org.apache.hadoop.hbase.regionserver.TestSplitLogWorker
> Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.737 sec <<< FAILURE!
> Failed tests:
>     testAcquireTaskAtStartup(org.apache.hadoop.hbase.regionserver.TestSplitLogWorker): ctr=0, oldval=0, newval=1
> {noformat}
> Bisecting commits on 0.94 branch, using (up to) 50 repetitions to include or exclude, I get:
> {noformat}
> 8cc5a5f481aeaf6debfa95110c4392d9c3ea20ca is the first bad commit
> commit 8cc5a5f481aeaf6debfa95110c4392d9c3ea20ca
>     HBASE-7172 TestSplitLogManager.testVanishingTaskZNode() fails when run individually and is flaky
>     git-svn-id: https://svn.apache.org/repos/asf/hbase/branches/0.94@1414975 13f79535-47bb-0310-9956-ffa450edef68
> {noformat}
> Will try again to see if the search ends in the same place.

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