[
https://issues.apache.org/jira/browse/ACCUMULO-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated ACCUMULO-2913:
---------------------------------
Description:
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.
was:
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 for the general cleanup to make the tests not fail
incorrectly.
> 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)
