[jira] [Commented] (HBASE-6826) [WINDOWS] TestFromClientSide failures
[
https://issues.apache.org/jira/browse/HBASE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722676#comment-13722676
]
Lars Hofhansl commented on HBASE-6826:
--
Committed to 0.94 as well.
> [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.95.2
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Labels: windows
> Fix For: 0.95.0, 0.94.11
>
> 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
[jira] [Commented] (HBASE-6826) [WINDOWS] TestFromClientSide failures
[
https://issues.apache.org/jira/browse/HBASE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722669#comment-13722669
]
Lars Hofhansl commented on HBASE-6826:
--
I ran TestFromClientSide locally, all good.
> [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.95.2
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Labels: windows
> Fix For: 0.95.0, 0.94.11
>
> 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
[jira] [Commented] (HBASE-6826) [WINDOWS] TestFromClientSide failures
[
https://issues.apache.org/jira/browse/HBASE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722655#comment-13722655
]
Lars Hofhansl commented on HBASE-6826:
--
Test only change. Looks good.
I'll commit this to 0.94 as well.
> [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.95.2
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Labels: windows
> Fix For: 0.95.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
[jira] [Commented] (HBASE-6826) [WINDOWS] TestFromClientSide failures
[
https://issues.apache.org/jira/browse/HBASE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722216#comment-13722216
]
Liang Xie commented on HBASE-6826:
--
seems it's not in 0.94 yet, [~lhofhansl], would you like take it in? i observed
testClientPoolRoundRobin failure today in our 0.94.3 codebase. thanks
> [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.95.2
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Labels: windows
> Fix For: 0.95.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
[jira] [Commented] (HBASE-6826) [WINDOWS] TestFromClientSide failures
[
https://issues.apache.org/jira/browse/HBASE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493629#comment-13493629
]
Hudson commented on HBASE-6826:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #253 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/253/])
HBASE-6826. [WINDOWS] TestFromClientSide failures (Revision 1407285)
Result = FAILURE
enis :
Files :
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java
> [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
[jira] [Commented] (HBASE-6826) [WINDOWS] TestFromClientSide failures
[
https://issues.apache.org/jira/browse/HBASE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493610#comment-13493610
]
Hudson commented on HBASE-6826:
---
Integrated in HBase-TRUNK #3522 (See
[https://builds.apache.org/job/HBase-TRUNK/3522/])
HBASE-6826. [WINDOWS] TestFromClientSide failures (Revision 1407285)
Result = FAILURE
enis :
Files :
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java
> [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
[jira] [Commented] (HBASE-6826) [WINDOWS] TestFromClientSide failures
[
https://issues.apache.org/jira/browse/HBASE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487520#comment-13487520
]
stack commented on HBASE-6826:
--
+1 on commit
> [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,
> 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
[jira] [Commented] (HBASE-6826) [WINDOWS] TestFromClientSide failures
[
https://issues.apache.org/jira/browse/HBASE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487372#comment-13487372
]
Hadoop QA commented on HBASE-6826:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12551427/hbase-6826_v2-trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated
85 warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 3 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/3189//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3189//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3189//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3189//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3189//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3189//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3189//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,
> 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
[jira] [Commented] (HBASE-6826) [WINDOWS] TestFromClientSide failures
[
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
