hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8700) IntegrationTestBigLinkedList can fail due to random number collision
Date Wed, 12 Jun 2013 02:51:20 GMT

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

Hadoop QA commented on HBASE-8700:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12587355/HBASE-8700-0.94.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified
tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/6011//console

This message is automatically generated.
                
> IntegrationTestBigLinkedList can fail due to random number collision
> --------------------------------------------------------------------
>
>                 Key: HBASE-8700
>                 URL: https://issues.apache.org/jira/browse/HBASE-8700
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HBASE-8700-0.94.patch, HBASE-8700-v0.patch, HBASE-8700-v1.patch
>
>
> The test can fail due to random number collision, claiming there are unreferenced elements
for obvious reasons (we rewrite some link). Original Accumulo test has one-stage generation
so it doesn't count unreferenced elements as failures, only undefined ones. With 200m longs
out of half-long range the probability of collision is approx 0.2%.
> Moreover, without some way to debug, it's hard to debug what keys should be looked at
in such cases

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message