[ https://issues.apache.org/jira/browse/PHOENIX-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151674#comment-16151674 ]
Hadoop QA commented on PHOENIX-4110: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12885120/PHOENIX-4110_addendum_4.x-HBase-0.98.patch against 4.x-HBase-0.98 branch at commit 21630d85f06d12db4b75776eb708814a0c360ec5. ATTACHMENT ID: 12885120 {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 javac{color}. The applied patch does not increase the total number of javac compiler 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:red}-1 core tests{color}. The patch failed these unit tests: Test results: https://builds.apache.org/job/PreCommit-PHOENIX-Build/1362//testReport/ Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/1362//console This message is automatically generated. > Shutdown mini cluster when number of tables grows beyond a threshold > -------------------------------------------------------------------- > > Key: PHOENIX-4110 > URL: https://issues.apache.org/jira/browse/PHOENIX-4110 > Project: Phoenix > Issue Type: Bug > Reporter: Samarth Jain > Assignee: Samarth Jain > Attachments: PHOENIX-4110_addendum_4.x-HBase-0.98.patch, > PHOENIX-4110.patch, PHOENIX-4110_v10.patch, PHOENIX-4110_v10.patch, > PHOENIX-4110_V2_4.x-HBase-0.98.patch, PHOENIX-4110_v3_4.x-HBase-0.98.patch, > PHOENIX-4110_v3.patch, PHOENIX-4110_v4.patch, PHOENIX-4110_v5.patch, > PHOENIX-4110_v6.patch, PHOENIX-4110_v7.patch, PHOENIX-4110_v8.patch, > PHOENIX-4110_v9.patch > > > ParallelRunListener today monitors the number of tests that have been run to > determine when mini cluster should be shut down. This helps prevent our test > JVM forks running in OOM. A better heuristic would be to instead check the > number of tables that were created by tests. This way when a particular test > class has created lots of tables, we can shut down the mini cluster sooner. -- This message was sent by Atlassian JIRA (v6.4.14#64029)