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

Hudson commented on HBASE-21168:
--------------------------------

Results for branch branch-2.1
        [build #316 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/316/]: 
(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/branch-2.1/316//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/branch-2.1/316//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/316//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


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


> BloomFilterUtil uses hardcoded randomness
> -----------------------------------------
>
>                 Key: HBASE-21168
>                 URL: https://issues.apache.org/jira/browse/HBASE-21168
>             Project: HBase
>          Issue Type: Task
>    Affects Versions: 2.0.0
>            Reporter: Mike Drob
>            Assignee: Mike Drob
>            Priority: Minor
>             Fix For: 3.0.0, 1.5.0, 1.3.3, 1.2.8, 2.2.0, 1.4.8, 2.1.1
>
>         Attachments: HBASE-21168.branch-1.002.patch, 
> HBASE-21168.master.001.patch, HBASE-21168.master.002.patch
>
>
> This was flagged by a Fortify scan and while it doesn't appear to be a real 
> issue, it's pretty easy to take care of anyway.
> The hard coded rand can be moved to the test class that actually needs it to 
> make the static analysis happy.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to