hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14535) Unit test for rpc connection concurrency / deadlock testing
Date Tue, 06 Oct 2015 17:41:26 GMT

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

stack commented on HBASE-14535:

bq.  I imagine we take a look at it rather than classify as a flaky test.

Thanks for the explanation.

How to designate difference between a flakey and a test that might fail with 'real' issue
that needs looking at? An outsider like myself trying to cleanup test failures would need
to be able to distinguish between the two. Devs trying to get a clean run against their patch
would need to be able to look at results and see that the fail was not theirs but because
the test is a 'non-deterministic'.

> Unit test for rpc connection concurrency / deadlock testing 
> ------------------------------------------------------------
>                 Key: HBASE-14535
>                 URL: https://issues.apache.org/jira/browse/HBASE-14535
>             Project: HBase
>          Issue Type: Sub-task
>          Components: rpc
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 2.0.0, 1.2.0, 1.3.0, 1.0.3, 1.1.3, 0.98.16
>         Attachments: hbase-14535_v1.patch, hbase-14535_v2.patch
> As per parent jira and recent jiras  HBASE-14449 + HBASE-14241 and HBASE-14313, we seem
to be lacking some testing rpc connection concurrency issues in a UT env. 

This message was sent by Atlassian JIRA

View raw message