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

Hudson commented on HBASE-27563:
--------------------------------

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


> ChaosMonkey sometimes generates invalid boundaries for random item selection
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-27563
>                 URL: https://issues.apache.org/jira/browse/HBASE-27563
>             Project: HBase
>          Issue Type: Bug
>          Components: integration tests
>    Affects Versions: 2.6.0, 3.0.0-alpha-4, 2.4.16, 2.5.3
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Minor
>             Fix For: 2.6.0, 3.0.0-alpha-4, 2.4.16, 2.5.3
>
>
> While running chaos monkey, I occasionally see `IndexOutOfBoundsException` 
> originating from `PolicyBasedChaosMonkey#selectRandomItems`. Looks like we 
> make some false assumptions about the arguments passes to the function. 



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

Reply via email to