You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Jordan Zimmerman (Jira)" <ji...@apache.org> on 2020/03/23 20:12:00 UTC

[jira] [Resolved] (CURATOR-564) Changes to retry failed TestingServer starts should be applied to TestingCluster

     [ https://issues.apache.org/jira/browse/CURATOR-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jordan Zimmerman resolved CURATOR-564.
--------------------------------------
    Resolution: Fixed

> Changes to retry failed TestingServer starts should be applied to TestingCluster
> --------------------------------------------------------------------------------
>
>                 Key: CURATOR-564
>                 URL: https://issues.apache.org/jira/browse/CURATOR-564
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 4.3.0
>            Reporter: Jordan Zimmerman
>            Assignee: Jordan Zimmerman
>            Priority: Major
>             Fix For: 5.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We recently made changes to catch server start issues (usually bind problems) which close the server and re-create/re-start it (see BaseClassForTests.setup). We should apply these to TestingCluster as well as we see Travis tests occasionally fail for TestingCluster startup issues.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)