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

Hudson commented on HBASE-19450:
--------------------------------

Results for branch branch-2.2
        [build #694 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/694/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/694//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/694//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/694//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Add log about average execution time for ScheduledChore
> -------------------------------------------------------
>
>                 Key: HBASE-19450
>                 URL: https://issues.apache.org/jira/browse/HBASE-19450
>             Project: HBase
>          Issue Type: Improvement
>          Components: Operability
>            Reporter: Reid Chan
>            Assignee: Reid Chan
>            Priority: Minor
>             Fix For: 3.0.0, 2.3.0, 2.1.8, 2.2.3
>
>         Attachments: HBASE-19450.master.001.patch, 
> HBASE-19450.master.002.patch, HBASE-19450.master.003.patch, 
> HBASE-19450.master.004.patch
>
>
> So far, there is no information about the exact execution time for a chore, 
> we can provide log information about it. It also brings other benefits, like 
> discovering inefficient chores which show rooms for improvement.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to