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 2009/06/16 12:01:07 UTC

[jira] Resolved: (DERBY-4270) Make replication tests save derby.log and database when a failure occurs.

     [ https://issues.apache.org/jira/browse/DERBY-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dag H. Wanvik resolved DERBY-4270.
----------------------------------

    Resolution: Fixed
    Derby Info:   (was: [Patch Available])

Committed patch derby-4270-2 as svn 785139, resolving.


> Make replication tests save derby.log and database when a failure occurs.
> -------------------------------------------------------------------------
>
>                 Key: DERBY-4270
>                 URL: https://issues.apache.org/jira/browse/DERBY-4270
>             Project: Derby
>          Issue Type: Improvement
>          Components: Replication, Test
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>            Priority: Minor
>             Fix For: 10.6.0.0
>
>         Attachments: derby-4270-2.diff, derby-4270-2.stat, derby-4270.diff
>
>
> Currently, derby.log is saved when a failure happens for most JUnit test. Replication tests use
> special subdirectories, so derby.log and the database files are not saved in the failure directory for these tests.
> It would be good to fix this to help diagnose intermittent errors.

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