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-2913) Continue stabilzation of replication UTs/ITs
Date Wed, 18 Jun 2014 16:00:26 GMT

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

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

Commit 643aaed80039f870a247f8c8e167152fd8b52b76 in accumulo's branch refs/heads/master from
[~elserj]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=643aaed ]

ACCUMULO-2913 More replication test stabilization.

Remove commented code, retry some checks for replication data a few times before
failing the test, and remove the defaultTimeoutSeconds because it was overriding
what was actually configured in the JUnit timeout annotation.


> Continue stabilzation of replication UTs/ITs
> --------------------------------------------
>
>                 Key: ACCUMULO-2913
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2913
>             Project: Accumulo
>          Issue Type: Task
>          Components: replication, test
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 1.7.0
>
>
> I've had the unit tests and integration tests for the replication work running in a nightly
jenkins job for the last month now. While it was meant to catch regressions then, it really
just catches weird timings in the test cases themselves (e.g. didn't wait long enough for
the replication table to exist, permissions didn't propagate through ZooCache, etc).
> This ticket is meant to continue the general cleanup to make the tests not fail incorrectly.



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

Mime
View raw message