[
https://issues.apache.org/jira/browse/HBASE-19827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333010#comment-16333010
]
Hudson commented on HBASE-19827:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4432 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/4432/])
HBASE-19827 Addendum for Flakey TestAssignmentManager Don't clear old (stack:
rev fa66c7e28e886857204dc2ce10f65b5fe264564b)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/ServerCrashProcedure.java
Revert "HBASE-19827 Addendum for Flakey TestAssignmentManager" Premature
(stack: rev c66b42fd9d1e4336352edf6851e4caa2ce0295d1)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/ServerCrashProcedure.java
> Addendum for Flakey TestAssignmentManager
> -----------------------------------------
>
> Key: HBASE-19827
> URL: https://issues.apache.org/jira/browse/HBASE-19827
> Project: HBase
> Issue Type: Sub-task
> Components: flakey, test
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 2.0.0-beta-2
>
> Attachments: HBASE-19827.master.001.patch,
> HBASE-19827.master.002.patch
>
>
> Addendum for parent. Rather than reopen parent for third time, doing subtask.
> So, in parent, we committed two fixes for failures seen in the random
> assignment test portion of TestAssignmentManager. The second fix almost works
> but in operation, a vital piece of info has been cleared because of the order
> in which stuff runs.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
