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

Hudson commented on HBASE-20173:
--------------------------------

Results for branch branch-2
        [build #482 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/482/]: 
(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/482//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/482//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/482//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


> [AMv2] DisableTableProcedure concurrent to ServerCrashProcedure can deadlock
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-20173
>                 URL: https://issues.apache.org/jira/browse/HBASE-20173
>             Project: HBase
>          Issue Type: Sub-task
>          Components: amv2
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: HBASE-20173.branch-2.001.patch, 
> HBASE-20173.branch-2.002.patch
>
>
> See 'Deadlock' scenario in parent issue. Doing as focused subtask since 
> parent has a few things going on in it.



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

Reply via email to