[jira] [Commented] (HBASE-8428) Tighten up IntegrationTestsDriver filter
[ https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642683#comment-13642683 ] Hudson commented on HBASE-8428: --- Integrated in hbase-0.95 #163 (See [https://builds.apache.org/job/hbase-0.95/163/]) HBASE-8428 Tighten up IntegrationTestsDriver filter (Revision 1475995) Result = FAILURE stack : Files : * /hbase/branches/0.95/hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestsDriver.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java * /hbase/branches/0.95/src/main/docbkx/developer.xml Tighten up IntegrationTestsDriver filter Key: HBASE-8428 URL: https://issues.apache.org/jira/browse/HBASE-8428 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Fix For: 0.95.1 Attachments: 8428.txt Currently, filter that looks for IntegrationTests is broad. Reports loads of errors as we try to parse classes we don't care about. Let me tighten it up so it doesn't scare folks away. It is particular bad when being run against a distribute cluster when the test context is not all present; here there are lots of ERROR reports about classes not found. -- 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-8428) Tighten up IntegrationTestsDriver filter
[ https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642797#comment-13642797 ] Hudson commented on HBASE-8428: --- Integrated in hbase-0.95-on-hadoop2 #81 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/81/]) HBASE-8428 Tighten up IntegrationTestsDriver filter (Revision 1475995) Result = FAILURE stack : Files : * /hbase/branches/0.95/hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestsDriver.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java * /hbase/branches/0.95/src/main/docbkx/developer.xml Tighten up IntegrationTestsDriver filter Key: HBASE-8428 URL: https://issues.apache.org/jira/browse/HBASE-8428 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Fix For: 0.95.1 Attachments: 8428.txt Currently, filter that looks for IntegrationTests is broad. Reports loads of errors as we try to parse classes we don't care about. Let me tighten it up so it doesn't scare folks away. It is particular bad when being run against a distribute cluster when the test context is not all present; here there are lots of ERROR reports about classes not found. -- 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-8428) Tighten up IntegrationTestsDriver filter
[ https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642832#comment-13642832 ] Hudson commented on HBASE-8428: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #511 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/511/]) HBASE-8428 Tighten up IntegrationTestsDriver filter (Revision 1475996) Result = FAILURE stack : Files : * /hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestsDriver.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java * /hbase/trunk/src/main/docbkx/developer.xml Tighten up IntegrationTestsDriver filter Key: HBASE-8428 URL: https://issues.apache.org/jira/browse/HBASE-8428 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Fix For: 0.95.1 Attachments: 8428.txt Currently, filter that looks for IntegrationTests is broad. Reports loads of errors as we try to parse classes we don't care about. Let me tighten it up so it doesn't scare folks away. It is particular bad when being run against a distribute cluster when the test context is not all present; here there are lots of ERROR reports about classes not found. -- 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-8428) Tighten up IntegrationTestsDriver filter
[
https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641472#comment-13641472
]
stack commented on HBASE-8428:
--
For sample ugly ERROR spew, see this comment:
https://issues.apache.org/jira/browse/HBASE-8421?focusedCommentId=13641070page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13641070
Let me attach a patch that gets rid of the ERROR stuff, at least when searching
for IntegrationTests. It also prints out the list of found IntegrationTests (I
find this useful). I also messed w/ the command line util because IMO it
should take a '-h' arg w/o throwing exceptions and I also filled out the usage
a little so folks have better idea what the regex is about. it looks like this
now:
{code}
stack@stack-1:~$ ./hbase/bin/hbase --config /home/stack/hbase-conf
org.apache.hadoop.hbase.IntegrationTestsDriver --help
usage: bin/hbase org.apache.hadoop.hbase.IntegrationTestsDriver options
Options:
-h,--help Show usage
-r,--regex arg Java regex to use selecting tests to run: e.g. .*TestBig.*
will select all tests that include TestBig in their name.
Default: .*IntegrationTest.*
{code}
The IntegrationTestsDriver is a beautiful tool. Would be a shame if folks went
away because of spew.
Tighten up IntegrationTestsDriver filter
Key: HBASE-8428
URL: https://issues.apache.org/jira/browse/HBASE-8428
Project: HBase
Issue Type: Bug
Reporter: stack
Assignee: stack
Currently, filter that looks for IntegrationTests is broad. Reports loads of
errors as we try to parse classes we don't care about. Let me tighten it up
so it doesn't scare folks away.
It is particular bad when being run against a distribute cluster when the
test context is not all present; here there are lots of ERROR reports about
classes not found.
--
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-8428) Tighten up IntegrationTestsDriver filter
[
https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641477#comment-13641477
]
stack commented on HBASE-8428:
--
Now there is no more spew when I run the tool w/ this patch applied:
{code}
stack@stack-1:~$ ./hbase/bin/hbase --config /home/stack/hbase-conf
org.apache.hadoop.hbase.IntegrationTestsDriver
2013-04-24 23:16:29,292 DEBUG [main] hbase.ClassFinder: Will look for classes
in /home/stack/hbase-0.97.0-SNAPSHOT/lib/hbase-client-0.97.0-SNAPSHOT.jar
2013-04-24 23:16:29,293 DEBUG [main] hbase.ClassFinder: Will look for classes
in /home/stack/hbase-0.97.0-SNAPSHOT/lib/hbase-common-0.97.0-SNAPSHOT.jar
2013-04-24 23:16:29,293 DEBUG [main] hbase.ClassFinder: Will look for classes
in /home/stack/hbase-0.97.0-SNAPSHOT/lib/hbase-common-0.97.0-SNAPSHOT-tests.jar
2013-04-24 23:16:29,294 DEBUG [main] hbase.ClassFinder: Will look for classes
in /home/stack/hbase-0.97.0-SNAPSHOT/lib/hbase-examples-0.97.0-SNAPSHOT.jar
2013-04-24 23:16:29,294 DEBUG [main] hbase.ClassFinder: Will look for classes
in /home/stack/hbase-0.97.0-SNAPSHOT/lib/hbase-it-0.97.0-SNAPSHOT-tests.jar
2013-04-24 23:16:29,295 DEBUG [main] hbase.ClassFinder: Will look for classes
in /home/stack/hbase-0.97.0-SNAPSHOT/lib/hbase-prefix-tree-0.97.0-SNAPSHOT.jar
2013-04-24 23:16:29,295 DEBUG [main] hbase.ClassFinder: Will look for classes
in /home/stack/hbase-0.97.0-SNAPSHOT/lib/hbase-protocol-0.97.0-SNAPSHOT.jar
2013-04-24 23:16:29,295 DEBUG [main] hbase.ClassFinder: Will look for classes
in /home/stack/hbase-0.97.0-SNAPSHOT/lib/hbase-server-0.97.0-SNAPSHOT.jar
2013-04-24 23:16:29,296 DEBUG [main] hbase.ClassFinder: Will look for classes
in
/home/stack/hbase-0.97.0-SNAPSHOT/lib/hbase-server-0.97.0-SNAPSHOT-sources.jar
2013-04-24 23:16:29,296 DEBUG [main] hbase.ClassFinder: Will look for classes
in /home/stack/hbase-0.97.0-SNAPSHOT/lib/hbase-server-0.97.0-SNAPSHOT-tests.jar
2013-04-24 23:16:31,075 INFO [main] hbase.IntegrationTestsDriver: Found 8
integration tests to run:
2013-04-24 23:16:31,075 INFO [main] hbase.IntegrationTestsDriver: class
org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
2013-04-24 23:16:31,075 INFO [main] hbase.IntegrationTestsDriver: class
org.apache.hadoop.hbase.IntegrationTestDataIngestSlowDeterministic
2013-04-24 23:16:31,075 INFO [main] hbase.IntegrationTestsDriver: class
org.apache.hadoop.hbase.IntegrationTestLazyCfLoading
2013-04-24 23:16:31,075 INFO [main] hbase.IntegrationTestsDriver: class
org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv
2013-04-24 23:16:31,075 INFO [main] hbase.IntegrationTestsDriver: class
org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify
2013-04-24 23:16:31,075 INFO [main] hbase.IntegrationTestsDriver: class
org.apache.hadoop.hbase.IntegrationTestDataIngestWithChaosMonkey
2013-04-24 23:16:31,075 INFO [main] hbase.IntegrationTestsDriver: class
org.apache.hadoop.hbase.IntegrationTestRebalanceAndKillServersTargeted
2013-04-24 23:16:31,075 INFO [main] hbase.IntegrationTestsDriver: class
org.apache.hadoop.hbase.IntegrationTestManyRegions
.2013-04-24 23:16:31,231 INFO [main] hbase.ClusterManager: Running with SSH
user [] and options [null]
...
{code}
Tighten up IntegrationTestsDriver filter
Key: HBASE-8428
URL: https://issues.apache.org/jira/browse/HBASE-8428
Project: HBase
Issue Type: Bug
Reporter: stack
Assignee: stack
Attachments: 8428.txt
Currently, filter that looks for IntegrationTests is broad. Reports loads of
errors as we try to parse classes we don't care about. Let me tighten it up
so it doesn't scare folks away.
It is particular bad when being run against a distribute cluster when the
test context is not all present; here there are lots of ERROR reports about
classes not found.
--
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-8428) Tighten up IntegrationTestsDriver filter
[
https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641515#comment-13641515
]
Hadoop QA commented on HBASE-8428:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12580487/8428.txt
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 5 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1 release
audit warnings (more than the trunk's current 0 warnings).
{color:red}-1 lineLengths{color}. The patch introduces lines longer than
100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5447//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5447//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5447//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5447//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5447//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5447//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5447//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5447//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5447//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5447//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5447//console
This message is automatically generated.
Tighten up IntegrationTestsDriver filter
Key: HBASE-8428
URL: https://issues.apache.org/jira/browse/HBASE-8428
Project: HBase
Issue Type: Bug
Reporter: stack
Assignee: stack
Fix For: 0.95.1
Attachments: 8428.txt
Currently, filter that looks for IntegrationTests is broad. Reports loads of
errors as we try to parse classes we don't care about. Let me tighten it up
so it doesn't scare folks away.
It is particular bad when being run against a distribute cluster when the
test context is not all present; here there are lots of ERROR reports about
classes not found.
--
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-8428) Tighten up IntegrationTestsDriver filter
[
https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641938#comment-13641938
]
Nick Dimiduk commented on HBASE-8428:
-
{noformat}
+Pass code-h/code to get usage on this sweet tool.
{noformat}
hahaha.
+1
Tighten up IntegrationTestsDriver filter
Key: HBASE-8428
URL: https://issues.apache.org/jira/browse/HBASE-8428
Project: HBase
Issue Type: Bug
Reporter: stack
Assignee: stack
Fix For: 0.95.1
Attachments: 8428.txt
Currently, filter that looks for IntegrationTests is broad. Reports loads of
errors as we try to parse classes we don't care about. Let me tighten it up
so it doesn't scare folks away.
It is particular bad when being run against a distribute cluster when the
test context is not all present; here there are lots of ERROR reports about
classes not found.
--
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-8428) Tighten up IntegrationTestsDriver filter
[
https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641976#comment-13641976
]
Sergey Shelukhin commented on HBASE-8428:
-
{code} !c.getName().contains(IntegrationTestingUtility) {code}
Parent super that checks categories and stuff should already take care of that,
right?
You might want to change book and/or help to reflect that default regex is not
all-inclusive.
Tighten up IntegrationTestsDriver filter
Key: HBASE-8428
URL: https://issues.apache.org/jira/browse/HBASE-8428
Project: HBase
Issue Type: Bug
Reporter: stack
Assignee: stack
Fix For: 0.95.1
Attachments: 8428.txt
Currently, filter that looks for IntegrationTests is broad. Reports loads of
errors as we try to parse classes we don't care about. Let me tighten it up
so it doesn't scare folks away.
It is particular bad when being run against a distribute cluster when the
test context is not all present; here there are lots of ERROR reports about
classes not found.
--
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-8428) Tighten up IntegrationTestsDriver filter
[ https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641980#comment-13641980 ] Sergey Shelukhin commented on HBASE-8428: - Oh, I see the latter is already done. Tighten up IntegrationTestsDriver filter Key: HBASE-8428 URL: https://issues.apache.org/jira/browse/HBASE-8428 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Fix For: 0.95.1 Attachments: 8428.txt Currently, filter that looks for IntegrationTests is broad. Reports loads of errors as we try to parse classes we don't care about. Let me tighten it up so it doesn't scare folks away. It is particular bad when being run against a distribute cluster when the test context is not all present; here there are lots of ERROR reports about classes not found. -- 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-8428) Tighten up IntegrationTestsDriver filter
[ https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642327#comment-13642327 ] stack commented on HBASE-8428: -- bq. Parent super that checks categories and stuff should already take care of that, right? Parent class tries to load this unless I have this check and then fails because mini hdfs cluster is not in path and does the ugly ERROR. I'm presuming you are +1 on the patch [~sershe] and am going to commit... Hopefully ok w/ you. Tighten up IntegrationTestsDriver filter Key: HBASE-8428 URL: https://issues.apache.org/jira/browse/HBASE-8428 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Fix For: 0.95.1 Attachments: 8428.txt Currently, filter that looks for IntegrationTests is broad. Reports loads of errors as we try to parse classes we don't care about. Let me tighten it up so it doesn't scare folks away. It is particular bad when being run against a distribute cluster when the test context is not all present; here there are lots of ERROR reports about classes not found. -- 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-8428) Tighten up IntegrationTestsDriver filter
[ https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642397#comment-13642397 ] stack commented on HBASE-8428: -- Integration tests work w/ this patch. I tried it on a cluster. Yeah, its ugly. The alternative would be uglier (so my adjacent comment claims). Tighten up IntegrationTestsDriver filter Key: HBASE-8428 URL: https://issues.apache.org/jira/browse/HBASE-8428 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Fix For: 0.95.1 Attachments: 8428.txt Currently, filter that looks for IntegrationTests is broad. Reports loads of errors as we try to parse classes we don't care about. Let me tighten it up so it doesn't scare folks away. It is particular bad when being run against a distribute cluster when the test context is not all present; here there are lots of ERROR reports about classes not found. -- 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-8428) Tighten up IntegrationTestsDriver filter
[ https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642582#comment-13642582 ] Hudson commented on HBASE-8428: --- Integrated in HBase-TRUNK #4080 (See [https://builds.apache.org/job/HBase-TRUNK/4080/]) HBASE-8428 Tighten up IntegrationTestsDriver filter (Revision 1475996) Result = FAILURE stack : Files : * /hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestsDriver.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java * /hbase/trunk/src/main/docbkx/developer.xml Tighten up IntegrationTestsDriver filter Key: HBASE-8428 URL: https://issues.apache.org/jira/browse/HBASE-8428 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Fix For: 0.95.1 Attachments: 8428.txt Currently, filter that looks for IntegrationTests is broad. Reports loads of errors as we try to parse classes we don't care about. Let me tighten it up so it doesn't scare folks away. It is particular bad when being run against a distribute cluster when the test context is not all present; here there are lots of ERROR reports about classes not found. -- 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-8428) Tighten up IntegrationTestsDriver filter
[ https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641231#comment-13641231 ] Sergey Shelukhin commented on HBASE-8428: - Dup of HBASE-8297? Tighten up IntegrationTestsDriver filter Key: HBASE-8428 URL: https://issues.apache.org/jira/browse/HBASE-8428 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Currently, filter that looks for IntegrationTests is broad. Reports loads of errors as we try to parse classes we don't care about. Let me tighten it up so it doesn't scare folks away. It is particular bad when being run against a distribute cluster when the test context is not all present; here there are lots of ERROR reports about classes not found. -- 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-8428) Tighten up IntegrationTestsDriver filter
[ https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641235#comment-13641235 ] Sergey Shelukhin commented on HBASE-8428: - the problem is that name filter is applied after classes are loaded, so it loads all and sundry and then filters it out Tighten up IntegrationTestsDriver filter Key: HBASE-8428 URL: https://issues.apache.org/jira/browse/HBASE-8428 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Currently, filter that looks for IntegrationTests is broad. Reports loads of errors as we try to parse classes we don't care about. Let me tighten it up so it doesn't scare folks away. It is particular bad when being run against a distribute cluster when the test context is not all present; here there are lots of ERROR reports about classes not found. -- 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
