[
https://issues.apache.org/jira/browse/DERBY-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631256#comment-13631256
]
Dag H. Wanvik commented on DERBY-6179:
--------------------------------------
Commit message:
Patch replscratch: checks the availability of the ports needed for the
replication test testReplication_Local_TestStraightReplication (the
first fixture) of the first test in the replication suite. This should
make it readily apparent in test log if there is such a
problem. Presently one needs to dig into the master or slaves' log
files to find that root cause.
> 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
