[
https://issues.apache.org/jira/browse/CURATOR-564?focusedWorklogId=408237&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-408237
]
ASF GitHub Bot logged work on CURATOR-564:
------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Mar/20 20:12
Start Date: 23/Mar/20 20:12
Worklog Time Spent: 10m
Work Description: Randgalt commented on pull request #351: [CURATOR-564]
catch startup issues for TestingCluster
URL: https://github.com/apache/curator/pull/351
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 408237)
Time Spent: 20m (was: 10m)
> 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: 20m
> 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)
