Sean Busbey commented on HBASE-15887:

Lastly, I do not print out the log lines as I am doing a rather crude grep for 
LOG.<level> entries right now which look pretty gnarly. However, I would like 
to see this go to Yetus and use something like Eclipse's AST support to 
properly find log entry parameters and calls.

We could also switch to pre/post  checking of the files that are marked as 
changing in the patch. then the grep would result in getting file names and 
lines. I don't think that's needed for this to be incrementally useful though. 
Maybe though? I feel like every time we add a test we get to "this should log a 
file" and then "that file should be in the qabot footer" in short order. How 
much time are you up for putting into this up front vs later down the line as 

> Report Log Additions and Removals in Builds
> -------------------------------------------
>                 Key: HBASE-15887
>                 URL: https://issues.apache.org/jira/browse/HBASE-15887
>             Project: HBase
>          Issue Type: New Feature
>          Components: build
>            Reporter: Clay B.
>            Assignee: Clay B.
>            Priority: Trivial
>         Attachments: HBASE-15887-v1.txt
> It would be very nice for the Apache Yetus verifications of HBase patches to 
> report log item addition and deletions.
> This is not my idea but [~mbm] asked if we could modify the personality for 
> reporting log additions and removals yesterday at an [HBase meetup at Splice 
> machine|http://www.meetup.com/hbaseusergroup/events/230547750/] as [~aw] 
> presented Apache Yetus for building HBase.

This message was sent by Atlassian JIRA

Reply via email to