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

Hudson commented on HBASE-23815:
--------------------------------

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




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1626//JDK8_Nightly_Build_Report_(Hadoop2)/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1626//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


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


> [Flakey Test] AbstractTestAsyncTableRegionReplicasRead family of tests fails 
> with no breadcrumbs on why
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-23815
>                 URL: https://issues.apache.org/jira/browse/HBASE-23815
>             Project: HBase
>          Issue Type: Bug
>          Components: flakies
>            Reporter: Michael Stack
>            Assignee: Michael Stack
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0
>
>
> Running locally w/ upped forkcount and maven threading > 1, the set of tests 
> that are derived from AbstractTestAsyncTableRegionReplicasRead fail near each 
> time often the only ones failed (Get and Scan tests). They don't give clues 
> why died. The xml has no info in it and no -output.txt is dropped. The .txt 
> just says failed startup.
> I've tried giving the forked jvms more RAM, messed w/ file counts....  
> Removing all of the custom setup seems to be a breakthrough. Let me put up a 
> patch.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to