[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603483#action_12603483 ]
V.Narayanan commented on DERBY-3632: ------------------------------------ In addition to the 7 failures in tinderbox, I had Derby-3689 recurring. These don't seem to be related to the patch. I am going to commit this patch. Thanks for the patch Ole. > Replication tests must ensure stable replication state has been reached > before attempting further connection or new replication commands. > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-3632 > URL: https://issues.apache.org/jira/browse/DERBY-3632 > Project: Derby > Issue Type: Bug > Components: Replication, Test > Affects Versions: 10.4.1.4, 10.5.0.0 > Environment: All > Reporter: Ole Solberg > Assignee: Ole Solberg > Priority: Minor > Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt > > > When executing replication commands (startslave, startmaster, stopmaster, > stopslave, failover) tests must make sure that correct replication state has > been reached before attempting further connection to the master and slave > databases. > This causes intermittent errors in replication tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.