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 2011/01/20 20:18:44 UTC

[jira] Issue Comment Edited: (DERBY-4980) Replication tests lose derby.log for slave

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

Dag H. Wanvik edited comment on DERBY-4980 at 1/20/11 2:17 PM:
---------------------------------------------------------------

The behavior was introduced by DERBY-4417 (since 10.6), revision 894607.


      was (Author: dagw):
    The behavior was introduced by DERBY-4417 (since 10.6).

  
> Replication tests lose derby.log for slave
> ------------------------------------------
>
>                 Key: DERBY-4980
>                 URL: https://issues.apache.org/jira/browse/DERBY-4980
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.6.1.0, 10.6.2.1, 10.7.1.1
>            Reporter: Dag H. Wanvik
>         Attachments: derby-4980-1.diff
>
>
> After running  ReplicationRun_Local_3_p1 I notice that of the two directories created, db_master and db_slave, only db_master contains a derby.log file. This is not so nice, since the log file is sometimes needed for test debugging ;-)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.