[jira] [Commented] (HBASE-12153) Fixing TestReplicaWithCluster
[ https://issues.apache.org/jira/browse/HBASE-12153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156252#comment-14156252 ] Nicolas Liochon commented on HBASE-12153: - Yeah, I actually don't like much timeouts in tests because they have do be removed during debugging sessions (the test is from me, but the timeouts are from Stack ;-) ). It's a workaround for surefire zombies... +1 for the patch. Fixing TestReplicaWithCluster - Key: HBASE-12153 URL: https://issues.apache.org/jira/browse/HBASE-12153 Project: HBase Issue Type: Bug Components: test Affects Versions: 1.0.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Priority: Trivial Fix For: 1.0.0 Attachments: 0001-FixTestReplicaWithCluster.patch This test takes about 30 ~ 40 seconds depending upon the resources available. Doesn't make sense to have such a tight bound(30s) on the unit test. [~nkeywal], what do you think ? Did you intend to have such a tight bound while adding the test here ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12153) Fixing TestReplicaWithCluster
[ https://issues.apache.org/jira/browse/HBASE-12153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156914#comment-14156914 ] Hudson commented on HBASE-12153: FAILURE: Integrated in HBase-TRUNK #5607 (See [https://builds.apache.org/job/HBase-TRUNK/5607/]) HBASE-12153 Fixing TestReplicaWithCluster (Manukranth Kolloju) (stack: rev 2c8f6b66cf31d3569de6626686d4ac5bf67e8efe) * hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestReplicaWithCluster.java Fixing TestReplicaWithCluster - Key: HBASE-12153 URL: https://issues.apache.org/jira/browse/HBASE-12153 Project: HBase Issue Type: Bug Components: test Affects Versions: 1.0.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Priority: Trivial Fix For: 2.0.0, 0.99.1 Attachments: 0001-FixTestReplicaWithCluster.patch This test takes about 30 ~ 40 seconds depending upon the resources available. Doesn't make sense to have such a tight bound(30s) on the unit test. [~nkeywal], what do you think ? Did you intend to have such a tight bound while adding the test here ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12153) Fixing TestReplicaWithCluster
[ https://issues.apache.org/jira/browse/HBASE-12153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156950#comment-14156950 ] Manukranth Kolloju commented on HBASE-12153: Thanks for committing [~stack] Fixing TestReplicaWithCluster - Key: HBASE-12153 URL: https://issues.apache.org/jira/browse/HBASE-12153 Project: HBase Issue Type: Bug Components: test Affects Versions: 1.0.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Priority: Trivial Fix For: 2.0.0, 0.99.1 Attachments: 0001-FixTestReplicaWithCluster.patch This test takes about 30 ~ 40 seconds depending upon the resources available. Doesn't make sense to have such a tight bound(30s) on the unit test. [~nkeywal], what do you think ? Did you intend to have such a tight bound while adding the test here ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12153) Fixing TestReplicaWithCluster
[ https://issues.apache.org/jira/browse/HBASE-12153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156996#comment-14156996 ] Hudson commented on HBASE-12153: FAILURE: Integrated in HBase-1.0 #260 (See [https://builds.apache.org/job/HBase-1.0/260/]) HBASE-12153 Fixing TestReplicaWithCluster (Manukranth Kolloju) (stack: rev 5aea36d4d43cfae7206a96b0a5630143822b4d75) * hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestReplicaWithCluster.java Fixing TestReplicaWithCluster - Key: HBASE-12153 URL: https://issues.apache.org/jira/browse/HBASE-12153 Project: HBase Issue Type: Bug Components: test Affects Versions: 1.0.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Priority: Trivial Fix For: 2.0.0, 0.99.1 Attachments: 0001-FixTestReplicaWithCluster.patch This test takes about 30 ~ 40 seconds depending upon the resources available. Doesn't make sense to have such a tight bound(30s) on the unit test. [~nkeywal], what do you think ? Did you intend to have such a tight bound while adding the test here ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12153) Fixing TestReplicaWithCluster
[
https://issues.apache.org/jira/browse/HBASE-12153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156107#comment-14156107
]
Hadoop QA commented on HBASE-12153:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12672492/0001-FixTestReplicaWithCluster.patch
against trunk revision .
ATTACHMENT ID: 12672492
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.master.TestDistributedLogSplitting
{color:red}-1 core zombie tests{color}. There are 2 zombie test(s):
at
org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFilesSplitRecovery.testSplitWhileBulkLoadPhase(TestLoadIncrementalHFilesSplitRecovery.java:339)
at
org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFiles.testSimpleLoad(TestLoadIncrementalHFiles.java:100)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11183//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11183//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11183//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11183//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11183//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11183//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11183//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11183//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11183//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11183//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11183//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11183//console
This message is automatically generated.
Fixing TestReplicaWithCluster
-
Key: HBASE-12153
URL: https://issues.apache.org/jira/browse/HBASE-12153
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 1.0.0
Reporter: Manukranth Kolloju
Assignee: Manukranth Kolloju
Priority: Trivial
Fix For: 1.0.0
Attachments: 0001-FixTestReplicaWithCluster.patch
This test takes about 30 ~ 40 seconds depending upon the resources available.
Doesn't make sense to have such a tight bound(30s) on the unit test.
[~nkeywal], what do you think ? Did you intend to have such a tight bound
while adding the test here ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
