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

Hudson commented on HBASE-27818:
--------------------------------

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

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/827/General_20Nightly_20Build_20Report/]




(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/827/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/827/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


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


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


> Split TestReplicationDroppedTables
> ----------------------------------
>
>                 Key: HBASE-27818
>                 URL: https://issues.apache.org/jira/browse/HBASE-27818
>             Project: HBase
>          Issue Type: Improvement
>          Components: Replication, test
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 2.6.0, 3.0.0-alpha-4, 2.5.5, 2.4.18
>
>
> It is flaky in pre commit for a long time, usually because of time out. But 
> it always pass for me locally, as well as in nightly job(that's also why it 
> does not in the flaky list
> It has 4 tests, not sure which one is the criminal, so I think we could split 
> it into 4 standalone tests, so if it still fails, we can find out the actual 
> flaky one.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to