db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DERBY-6179) Insert some guarding code into the first replication test to check port availability
Date Tue, 21 May 2013 11:25:16 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662900#comment-13662900
] 

Dag H. Wanvik edited comment on DERBY-6179 at 5/21/13 11:23 AM:
----------------------------------------------------------------

Haven't seen this this lately. Probably Knut's killing off old processes in the test lab solved
the issue, so closing this for now. I'll leave this code in place in case since it makes the
test more robust. 
                
      was (Author: dagw):
    Haven't seen this this lately. Probably Knut's killing off old processes in the test lab
solved the issue, so closing this for now. I'll leave this codein place in case since it makes
the test more robust. 
                  
> 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

Mime
View raw message