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 Tue, 17 Jun 2014 00:07:04 GMT

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

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

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

ACCUMULO-2913 Some stabilization on MultiInstanceReplicationIT

Saw this one fail with no records in the peer, but it looks like we just expected
the records to be there before they actually made it.


> 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