[jira] [Commented] (HBASE-8009) Fix and reenable the hbase-example unit tests.

["Anoop Sam John (JIRA)" <ji...@apache.org>]

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

Anoop Sam John commented on HBASE-8009:
---------------------------------------

[~stack] Most of the failed cases I can see a failure with TestBulkDeleteProtocol#testBulkDeleteColumn(). Here in the test I am deleting 100 rows and asserting that against what the HTable#coprocessorExec() returned me. This in the failed case coming as 120 instead of 100.  In test I have total 5 regions in table with 20 rows each. So one region entry coming as duplicate in the Map (return value from HTable#coprocessorExec () )!!! Some retry issue!!!( ? )
I started digging in the coprocessorExec() code more.. Seems there are some bugs in that area. Let me explore.  BTW will it be good that I add some logs in the test case about the returned Map from coprocessorExec() and give a patch. Can we commit so that the next failed time we can get more clear picture about our doubt?
                
> Fix and reenable the hbase-example unit tests.
> ----------------------------------------------
>
>                 Key: HBASE-8009
>                 URL: https://issues.apache.org/jira/browse/HBASE-8009
>             Project: HBase
>          Issue Type: Task
>          Components: test
>            Reporter: stack
>            Priority: Critical
>
> The unit tests pass locally for me repeatedly but fail from time to time up on jenkins.  HBASE-7994 disabled them.  This issue is about spending the time to make sure they pass up on jenkins again.  They have been disabled because unit tests have been failing way more often than they have been passing over the last few months and we want to establish passing tests as the precedent again.  Once that is in place, we can work on bringing back examples.

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