[
https://issues.apache.org/jira/browse/HBASE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465134#comment-13465134
]
Hadoop QA commented on HBASE-6826:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12546126/hbase-6826_v1-trunk.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2951//console
This message is automatically generated.
> [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
> Attachments: hbase-6826_v1-0.94.patch, hbase-6826_v1-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