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

genericqa commented on HADOOP-14652:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  6s{color} 
| {color:red} HADOOP-14652 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-14652 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12886755/HADOOP-14652.005.patch
 |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/14230/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Update metrics-core version to 3.2.4
> ------------------------------------
>
>                 Key: HADOOP-14652
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14652
>             Project: Hadoop Common
>          Issue Type: Sub-task
>    Affects Versions: 3.0.0-beta1
>            Reporter: Ray Chiang
>            Assignee: Ray Chiang
>            Priority: Major
>         Attachments: HADOOP-14652.001.patch, HADOOP-14652.002.patch, 
> HADOOP-14652.003.patch, HADOOP-14652.004.patch, HADOOP-14652.005.patch
>
>
> The current artifact is:
>     com.codehale.metrics:metrics-core:3.0.1
> That version could either be bumped to 3.0.2 (the latest of that line), or 
> use the latest artifact:
>     io.dropwizard.metrics:metrics-core:3.2.4



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to