You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2012/11/08 23:08:12 UTC

[jira] [Updated] (HBASE-6826) [WINDOWS] TestFromClientSide failures

     [ https://issues.apache.org/jira/browse/HBASE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Enis Soztutar updated HBASE-6826:
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.96.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

I've committed this. Thanks Stack for the review. 
                
> [WINDOWS] TestFromClientSide failures
> -------------------------------------
>
>                 Key: HBASE-6826
>                 URL: https://issues.apache.org/jira/browse/HBASE-6826
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.3, 0.96.0
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>              Labels: windows
>             Fix For: 0.96.0
>
>         Attachments: hbase-6826_v1-0.94.patch, hbase-6826_v1-trunk.patch, hbase-6826_v2-0.94.patch, hbase-6826_v2-trunk.patch
>
>
> The following tests fail for TestFromClientSide: 
> {code}
> testPoolBehavior()
> testClientPoolRoundRobin()
> testClientPoolThreadLocal()
> {code}
> The first test fails due to the fact that the test (wrongly) assumes that ThredPoolExecutor can reclaim the thread immediately. 
> The second and third tests seem to fail because that Put's to the table does not specify an explicit timestamp, but on windows, consecutive calls to put happen to finish in the same milisecond so that the resulting mutations have the same timestamp, thus there is only one version of the cell value.  

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