accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2194) Back-to-back Security randomwalk tests fail
Date Thu, 13 Mar 2014 14:43:45 GMT

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

ASF subversion and git services commented on ACCUMULO-2194:
-----------------------------------------------------------

Commit ea86b44dfd6f46d389a630beb33ac49b65d87cd7 in accumulo's branch refs/heads/1.6.0-SNAPSHOT
from [~bhavanki]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=ea86b44 ]

ACCUMULO-2194 Add delay for randomwalk Security teardown

If two Security randomwalk tests run back-to-back, the second test may see that the
table user still exists even though it was removed when the first test was torn down.
This can happen if the user drop does not propagate through Zookeeper quickly enough.
This commit adds a delay to the end of the Security test to give ZK some time.


> Back-to-back Security randomwalk tests fail
> -------------------------------------------
>
>                 Key: ACCUMULO-2194
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2194
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.4.4
>            Reporter: Bill Havanki
>            Assignee: Bill Havanki
>              Labels: randomwalk, test
>         Attachments: Security_failure_log.txt
>
>
> When the Security randomwalk test is run twice in a row by a higher-level test (e.g.,
ShortClean), the second Security test fails relatively quickly. A sample log is attached.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message