[
https://issues.apache.org/jira/browse/DERBY-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631579#comment-13631579
]
Knut Anders Hatlen commented on DERBY-6179:
-------------------------------------------
Looks like a good improvement. +1.
One small nit: If the no-arg waitForAvailablePort() had passed the value of the
default port instead of -1, we wouldn't need special handling of the magic
value -1 in the 1-arg variant of the method.
> Insert some guarding code into the first replication test to check port
> availability
> ------------------------------------------------------------------------------------
>
> Key: DERBY-6179
> URL: https://issues.apache.org/jira/browse/DERBY-6179
> Project: Derby
> Issue Type: Task
> Components: Replication, Test
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Attachments: replscratch.diff, replscratch.status
>
>
> We have seen lots of noise in the nightlies with replication failing. It
> seems that often it fails due to ports being unavailable, possibly due to
> earlier (failed) runs.
> This JIRA issue tracks diagnostic code I want to insert to see what's
> happening at test run time.
> The diagnostic code can be removed when we have stabilized the tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
