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] [Commented] (DERBY-6179) Insert some guarding code into the first replication test to check port availability
Date Thu, 18 Apr 2013 05:17:15 GMT

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

Dag H. Wanvik commented on DERBY-6179:
--------------------------------------

Committed simplification as suggested by Knut in svn 1469165.
I have now seen a test run failing with this instrumentation in place, but the checks did
not trigger anything; still the slave failed with
its port being used. In my stand-alone run, I see the port number is different at the place
of the failure, so I'll add some temporary verbose chatter (forgive!;-)  to the log of the
regression for a bit to see which ports are actually checked and compare that with the busy
port number. 
                
> 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