db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4199) Write exceptions to file in the fail directory as they occur with JUnit tests
Date Thu, 07 May 2009 12:32:30 GMT

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

Kristian Waagan updated DERBY-4199:
-----------------------------------

    Attachment: derby-4199-1a-writeExceptionsToFile.stat
                derby-4199-1a-writeExceptionsToFile.diff

I refreshed, and changed, the original patch.
Patch 1a will log exceptions to a file called 'error-stacktrace.out' in the same directory
as derby.log and the database are saved. If copying the log file or the database fail, that
exception will also be logged to the file.
To avoid overwriting potentially valuable information, the file is opened in append mode.
 The time and date are written as a header before the exception stack trace is written.

I have tested the patch manually (by throwing an exception in a test, and also by removing
the write privileges on the derby.log file), and will start the regression tests.
Patch ready for review.

> Write exceptions to file in the fail directory as they occur with JUnit tests
> -----------------------------------------------------------------------------
>
>                 Key: DERBY-4199
>                 URL: https://issues.apache.org/jira/browse/DERBY-4199
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.6.0.0
>            Reporter: Kathey Marsden
>            Assignee: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-4199-1a-writeExceptionsToFile.diff, derby-4199-1a-writeExceptionsToFile.stat
>
>
> It would be very helpful to write exceptions to the fail directory as they oiccur with
JUnit tests.    
> If tests hang we can still get the failure information and sometimes it is just more
efficient to be able to see failures as they occur.  Kristian attached a patch to DERBY-2667
for this but it no longer applies to trunk (derby-2667-WriteExceptionsToFileAsTheyHappen.diff).

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