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

Reply via email to