[
https://issues.apache.org/jira/browse/HBASE-25809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17331250#comment-17331250
]
Hudson commented on HBASE-25809:
--------------------------------
Results for branch branch-1
[build #117 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-1/117/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-1/117//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-1/117//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-1/117//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
> [branch-1] TestAtomicOperation.testMultiRowMutationMultiThreads deadlock
> ------------------------------------------------------------------------
>
> Key: HBASE-25809
> URL: https://issues.apache.org/jira/browse/HBASE-25809
> Project: HBase
> Issue Type: Bug
> Reporter: Andrew Kyle Purtell
> Assignee: Andrew Kyle Purtell
> Priority: Major
> Fix For: 1.7.0
>
>
> TestAtomicOperation.testMultiRowMutationMultiThreads deadlocks.
> There is an easy fix for the test that synchronizes on the CHM instead of the
> object. We already have a Findbugs exceptions for synchronization on the CHM
> and get-then-set on it is what we synchronizing for anyway.
> This is only relevant for branch-1 because we have to synchronize
> get-then-set due to Java 7 compatibility. For branch-2 and master we use
> CHM#computeIfPresent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
