[ 
https://issues.apache.org/jira/browse/HBASE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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

Reply via email to