[ 
https://issues.apache.org/jira/browse/HBASE-16308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408204#comment-15408204
 ] 

stack commented on HBASE-16308:
-------------------------------

Stuff passes locally of course. It started failing for all recent trunk builds. 
Seems to have started here:

Failed Build #1351 (Aug 4, 2016 5:25:17 AM)

add description
        Build Artifacts
        Changes
HBASE-16350 Undo server abort from HBASE-14968 (detail)
HBASE-16317 revert all ESAPI changes (detail)
HBASE-15574 Fix typo in HRegionServerCommandLine (detail)
        
Started by upstream project HBase-Trunk_matrix build number 1351
originally caused by:

Started by timer
        
This run spent:

1 hr 7 min waiting in the queue;
32 min building on an executor;
1 hr 40 min total from scheduled to completion.
        Revision: 0eaf3edc3acee3273126bd9a575401fcf85971b8
refs/remotes/origin/master
        Test Result (1 failure / ±0)
org.apache.hadoop.hbase.http.log.TestLogLevel.testDynamicLogLevel

I can look at this separately.

> Contain protobuf references
> ---------------------------
>
>                 Key: HBASE-16308
>                 URL: https://issues.apache.org/jira/browse/HBASE-16308
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Protobufs
>            Reporter: stack
>            Assignee: stack
>         Attachments: HBASE-16308.master.001.patch, 
> HBASE-16308.master.002.patch, HBASE-16308.master.003.patch, 
> HBASE-16308.master.004.patch, HBASE-16308.master.005.patch, 
> HBASE-16308.master.006.patch
>
>
> Clean up our protobuf references so contained to just a few classes rather 
> than being spread about the codebase. Doing this work will make it easier 
> landing the parent issue and will make it more clear where the division 
> between shaded protobuf and unshaded protobuf lies (we need to continue with 
> unshaded protobuf for HDFS references by AsyncWAL and probably EndPoint 
> Coprocessors)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to