You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2013/04/13 15:04:16 UTC
[jira] [Assigned] (DERBY-6179) Insert some guarding code into the
first replication test to check port availability
[ https://issues.apache.org/jira/browse/DERBY-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik reassigned DERBY-6179:
------------------------------------
Assignee: Dag H. Wanvik
> 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