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] Updated: (DERBY-4270) Make replication tests save derby.log and database when a failure occurs.
Date Fri, 12 Jun 2009 18:36:07 GMT

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

Dag H. Wanvik updated DERBY-4270:
---------------------------------

    Derby Info: [Patch Available]

> 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.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.


Mime
View raw message